Currently, PrestoParser only advertises public interfaces which do parsing + metadata resolution, there is no existing API for doing only the lexical parsing of a query to extract some set of query information.
The most obvious example of this would be if a caller wanted to know what tables a query will access without needing to resolve the table metadata through ConnectorMetadata. For some embedded scenarios, such as client-side pre-processing, fully parsing and analyzing the query into a logical plan may not be possible
I am not yet decided whether it makes sense to add an API to PrestoParser to do this, or to have a new interface. I will investigate and open a draft PR to get some comments on structuring
cc @mbasmanova