Add option to select SQL engine with each query. #160
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.
Signed-off-by: Yury-Fridlyand [email protected]
Description
This adds a new URL parameter
engine
, which controls SQL engine selection.Acceptable values (case insensitive):
v1
orlegacy
v2
If it is not given or has another value, the default strategy is used - V2 with fallback to V1.
Could be used for
_explain
request as well.These changes include also support of this parameter by SQL CLI and JDBC driver too.
Examples
Rest API
Add new parameter to URL (in any order):
Examples:
Query not supported by
V2
sent toV2
:Query not supported by
V1
sent toV1
:SQL CLI tool:
New command line option:
JDBC driver
Add new parameter to connection string (in any order)
Notes
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.