-
-
Notifications
You must be signed in to change notification settings - Fork 96
Don't allow field extractors to match field name suffixes #1447
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
Conversation
8aed1ef
to
216aa4a
Compare
216aa4a
to
cf8eb82
Compare
After thinking about this PR a bit, I think this might break queries like |
The bug that this PR fixes prevented those queries to work as well, so I don't think there is any harm done. |
Yeah, I agree. let's treat this as a separate feature that we don't support yet. If we stick with component-based suffix matching, we're good for this PR. |
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.
This is still missing a changelog entry, otherwise it is good to go.
Don't allow queries like `oo.x` to match a field `foo.x` anymore, since that can lead to unintuitive results for the user. Instead, require that full field names are matched. (So in the previous example, only `foo.x` and `x` would be valid suffix matches)
049ea9a
to
4677d3d
Compare
📔 Description
📝 Checklist
🎯 Review Instructions