What are the access paths that presto uses (full scan, range scan, skip scan, ...)? Does it understand indexes?
We currently have a pull request open right now that will allow range predicates to be be pushed into the connectors. This will allow connectors the ability to implement range/skip scans.
The core presto engine does not take advantage of indexes right now.