Skip to content

SQL: LIKE/RLIKE don't use underlying exact field #39442

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.

Sign up for GitHub

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

Jump to bottom
Closed
matriv opened this issue Feb 27, 2019 · 1 comment · Fixed by #39443
Closed

SQL: LIKE/RLIKE don't use underlying exact field #39442

matriv opened this issue Feb 27, 2019 · 1 comment · Fixed by #39443
Assignees
@matriv
Labels
:Analytics/SQL SQL querying >bug

Comments

@matriv
Copy link
Contributor

matriv commented Feb 27, 2019

For queries like: SELECT * FROM t WHERE text_field LIKE '%a%'
the text_field is used instead of the underlying exact field (e.g.: text_field.keyword)
@matriv matriv added >bug :Analytics/SQL SQL querying labels Feb 27, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@matriv matriv self-assigned this Feb 27, 2019
matriv added a commit to matriv/elasticsearch that referenced this issue Feb 27, 2019
@matriv
SQL: Use underlying exact field for LIKE/RLIKE
a1e5a04 
Previously, if a text field had an underlying keyword field
the latter was not used instead of the text leading to wrong
results returned by queries filtering with LIKE/RLIKE.

Fixes: elastic#39442
@matriv matriv mentioned this issue Feb 27, 2019
Merged
@matriv matriv changed the title SQL: LIKE/RLIKE don't peak up underlying exact field SQL: LIKE/RLIKE don't use underlying exact field Feb 27, 2019
matriv added a commit that referenced this issue Feb 27, 2019
@matriv
SQL: Use underlying exact field for LIKE/RLIKE (#39443)
2a5d0a3 
Previously, if a text field had an underlying keyword field
the latter was not used instead of the text leading to wrong
results returned by queries filtering with LIKE/RLIKE.

Fixes: #39442
matriv added a commit that referenced this issue Feb 27, 2019
@matriv
SQL: Use underlying exact field for LIKE/RLIKE (#39443)
a2c07b5 
Previously, if a text field had an underlying keyword field
the latter was not used instead of the text leading to wrong
results returned by queries filtering with LIKE/RLIKE.

Fixes: #39442
matriv added a commit that referenced this issue Feb 27, 2019
@matriv
SQL: Use underlying exact field for LIKE/RLIKE (#39443)
cfa6173 
Previously, if a text field had an underlying keyword field
the latter was not used instead of the text leading to wrong
results returned by queries filtering with LIKE/RLIKE.

Fixes: #39442
matriv added a commit that referenced this issue Feb 27, 2019
@matriv
SQL: Use underlying exact field for LIKE/RLIKE (#39443)
1608c9a 
Previously, if a text field had an underlying keyword field
the latter was not used instead of the text leading to wrong
results returned by queries filtering with LIKE/RLIKE.

Fixes: #39442
matriv added a commit that referenced this issue Feb 27, 2019
@matriv
SQL: Use underlying exact field for LIKE/RLIKE (#39443)
2075ca8 
Previously, if a text field had an underlying keyword field
the latter was not used instead of the text leading to wrong
results returned by queries filtering with LIKE/RLIKE.

Fixes: #39442
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matriv matriv

Labels
:Analytics/SQL SQL querying >bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

SQL: Use underlying exact field for LIKE/RLIKE matriv/elasticsearch
2 participants
@matriv @elasticmachine