[SPARK-17982][SQL][BACKPORT-2.0] SQLBuilder should wrap the generated SQL with parenthesis for LIMIT #15856
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.
What changes were proposed in this pull request?
Currently,
SQLBuilderhandlesLIMITby always addingLIMITat the end of the generated subSQL. It makesRuntimeExceptions like the following. This PR adds a parenthesis always exceptSubqueryAliasis used together withLIMIT.Before
After
Fixed cases in this PR
The following two cases are the detail query plans having problematic SQL generations.
SELECT * FROM (SELECT id FROM tbl LIMIT 2)Please note that FROM SELECT part of the generated SQL in the below. When we don't use '()' for limit, this fails.
SELECT * FROM (SELECT id FROM tbl TABLESAMPLE (2 ROWS))Please note that ((~~~) AS gen_subquery_0 LIMIT 2) in the below. When we use '()' for limit on
SubqueryAlias, this fails.How was this patch tested?
Pass the Jenkins test with a newly added test case.