Skip to content
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

SQL: Use underlying exact field for LIKE/RLIKE #39443

Merged
merged 1 commit into from Feb 27, 2019

Conversation

Projects
None yet
5 participants
@matriv
Copy link
Contributor

commented Feb 27, 2019

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

SQL: Use underlying exact field for LIKE/RLIKE
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
@elasticmachine

This comment has been minimized.

Copy link
Collaborator

commented Feb 27, 2019

@matriv matriv requested review from costin and astefan Feb 27, 2019

@astefan
Copy link
Contributor

left a comment

LGTM

@costin

costin approved these changes Feb 27, 2019

Copy link
Member

left a comment

Good catch. LGTM

@matriv matriv merged commit 2a5d0a3 into elastic:master Feb 27, 2019

8 checks passed

CLA Commit author has signed the CLA
Details
elasticsearch-ci/1 Build finished.
Details
elasticsearch-ci/2 Build finished.
Details
elasticsearch-ci/bwc Build finished.
Details
elasticsearch-ci/default-distro Build finished.
Details
elasticsearch-ci/docbldesx Build finished.
Details
elasticsearch-ci/oss-distro-docs Build finished.
Details
elasticsearch-ci/packaging-sample Build finished.
Details

@matriv matriv deleted the matriv:mt/fix-39442 branch Feb 27, 2019

matriv added a commit that referenced this pull request Feb 27, 2019

SQL: Use underlying exact field for LIKE/RLIKE (#39443)
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 pull request Feb 27, 2019

SQL: Use underlying exact field for LIKE/RLIKE (#39443)
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 pull request Feb 27, 2019

SQL: Use underlying exact field for LIKE/RLIKE (#39443)
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 pull request Feb 27, 2019

SQL: Use underlying exact field for LIKE/RLIKE (#39443)
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

This comment has been minimized.

Copy link
Contributor Author

commented Feb 27, 2019

Backported to 7.x with a2c07b5
to 7.0 with cfa6173
to 6.7 with 1608c9a
to 6.6 with 2075ca8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.