Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CATEGORY
Choose one
SUMMARY
Presto supports using the optional cluster when specifying the table name, i.e.,
[[cluster.]schema].table
however the currently SQL parse logic only returns at most the first two components, i.e.,cluster.schema
if a cluster was defined.This PR extends the logic to support the
[[cluster.]schema].table
construct as well as:get_real_name()
.get_real_name()
logic wasn't overly apparent though it's used when a table alias is present. I felt this logic wasn't overly clear and in the case of aTokenList
representingschema.table AS foo
theget_real_name()
only returnstable
(though this wasn't invoked because there was the.
token). From a table construct validity perspective it seems more prudent to strip the alias and then extract the full table name if valid.TEST PLAN
CI.
ADDITIONAL INFORMATION
REVIEWERS
to: @graceguo-supercat @michellethomas @mistercrunch