Add explicit EOF for expression parser and use assert instead of exception in sql planner #11041
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.
Description
This PR fixes 2 issues.
NoViableAltException
instance. This could be problematic for queries that Calcite needs to explore large space of candidate queries as the Antlr parser will create exceptions over again even though those exceptions are ignored. The below flame graph shows initializing exceptions was one of the most expensive parts for the query 19 (giant union query) in SqlBenchmark. Implicit EOF can also causeNoViableAltException
to be thrown incorrectly sometimes. This PR adds explicit EOF in the grammar file.getClass().getSimpleName()
inBottomUpTransform.checkedProcess()
can be expensive if it is called lots of times. This PR changes it to useassert
.SqlBenchmark.planSql()
results. Only the query 19 (the giant union query) shows a noticeable improvement.Key changed/added classes in this PR
Expr.g4
BottomUpTransform
This PR has: