-
Notifications
You must be signed in to change notification settings - Fork 141
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
Support simple_query_string function in SQL/PPL query engine #192
Comments
This was referenced May 12, 2022
Closed
MaxKsyunz
referenced
this issue
in Bit-Quill/opensearch-project-sql
May 14, 2022
…hub.com/Bit-Quill/opensearch-project-sql into dev-simple_query_string-#192-sql-simple
MaxKsyunz
referenced
this issue
in Bit-Quill/opensearch-project-sql
May 14, 2022
…l' into dev-simple_query_string-#192-sql-simple-max_ast
6 tasks
Yury-Fridlyand
referenced
this issue
in Bit-Quill/opensearch-project-sql
Jun 1, 2022
…v-simple_query_string-#192-impl2 Signed-off-by: Yury Fridlyand <[email protected]>
Yury-Fridlyand
referenced
this issue
in Bit-Quill/opensearch-project-sql
Jun 2, 2022
#192-impl2`, since that branch was corrupted by incorrect merge. Signed-off-by: Yury Fridlyand <[email protected]>
Yury-Fridlyand
referenced
this issue
in Bit-Quill/opensearch-project-sql
Jun 3, 2022
…ing-#192-impl3 Signed-off-by: Yury Fridlyand <[email protected]>
6 tasks
fixed by #635 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related design is presented in issue #182
Todo list
simple_query_string
functionality by pushing it down to the search enginesimple_query_string
function in SQL and PPL syntax and parser, including all the available parameterssimple_query_string
Function details
The
simple_query_string
function maps to the simple query string used in the search engine. This query returns documents based on a provided query string, using a parser with a limited but fault-tolerant syntax. While its syntax is more limited than the query_string query, the simple_query_string query does not return errors for invalid syntax. Instead, it ignores any invalid parts of the query string.Syntax:
simple_query_string([field_list, ] query_string_expression[, option=<option_value>]*)
Simple query string syntax:
The simple_query_string query supports the following operators:
+
signifies AND operation|
signifies OR operation-
negates a single token"
wraps a number of tokens to signify a phrase for searching*
at the end of a term signifies a prefix query( and )
signify precedence~N
after a word signifies edit distance (fuzziness)~N
after a phrase signifies slop amountFLAG valid values:
ALL
(Default) Enables all optional operators.AND
Enables the + AND operator.ESCAPE
Enables \ as an escape character.FUZZY
Enables the ~N operator after a word, where N is an integer denoting the allowed edit distance for matchingNEAR
Enables the ~N operator, after a phrase where N is the maximum number of positions allowed between matching tokens. Synonymous to SLOP.NONE
Disables all operators.NOT
Enables the - NOT operator.OR
Enables the | OR operator.PHRASE
Enables the " quotes operator used to search for phrases.PRECEDENCE
Enables the( and )
operators to control operator precedence.PREFIX
Enables the * prefix operator.SLOP
Enables the ~N operator, after a phrase where N is maximum number of positions allowed between matching tokens. Synonymous to NEAR.WHITESPACE
Enables whitespace as split characters.Available options:
Sample query:
The text was updated successfully, but these errors were encountered: