-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disallow unquoted literals in LIKE
clause in DESCRIBE
statement
#154
Disallow unquoted literals in LIKE
clause in DESCRIBE
statement
#154
Conversation
LIKE
clause
This comment was marked as abuse.
This comment was marked as abuse.
Signed-off-by: Yury-Fridlyand <[email protected]>
9eafb4a
to
0ec464a
Compare
LIKE
clauseLIKE
clause
LIKE
clauseLIKE
clause
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :D
FYI you spelled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. FYI you spelled unquoted
wrong in the branch names.
D'oh, again. I renamed integ branch, the dev one will be deleted after merge. |
} | ||
|
||
@Test | ||
public void describe_compatible_with_old_engine_syntax() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why remove the describe test case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I made it incompatible
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd make it clear in the title that only DESCRIBE
statement is affected.
LIKE
clauseLIKE
clause in DESCRIBE
statement
* Import h3 library (#154) Made following changes to make it compatible: 1. Rename package from elasticsearch to opensearch.geospatial 2. Update License headers 3. Update build file 4. Update settings to include sub projects * Use Transport Request (#164) Remove usage of deprecated BaseNodeRequest * Update http client package to resolve build failure (#168) (#171) * Introduce H3 min resolution constant (#165) H3 version 1 has 16 resolutions, numbered 0 through 15. Introduced a constant to represent min value, similar to max value. * Add geohex aggregation (#160) This aggregation will use uber's h3 to group coordinates into H3 cell. Created new aggregation type geohex_grid. The precision will be between 0 and 15. This aggreation has default precision as 5, similar to geohash and geotile. Signed-off-by: Vijayan Balasubramanian <[email protected]> * Add integration test (#176) Included integration test for geohex_grid. Signed-off-by: Vijayan Balasubramanian <[email protected]>
Signed-off-by: Yury-Fridlyand [email protected]
Description
Update SQL parser to disallow unquoted strings as identifiers wildcards clause.
To test this fix for opensearch-project#650 disable legacy engine first:
Before
With patch, without fix
After
Another queries for test:
and
Notes
As discussed, we should prohibit usage of raw identifies in SQL queries where wildcards are allowed. A user should specify string literal instead (a quoted string with
'
or"
). Backtick quote`
is not accepted.This behavior was copied from legacy engine and it is an erroneous approach.
The root cause of opensearch-project#650 is a
keywordsCanBeId
which was in the user query which cased V2 parser to fail and fall back to V1.Issues Resolved
opensearch-project#650
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.