fix: make eql_v2.compare robust against null search terms #127
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ProtectJS was generating null search terms and EQL was only checking for the presence of an index *key*, which would then end up checking if two JSONB null values were equal, which would always return true. This commit changes checks of the form: ``` val ? '<index-key>' ``` to ``` val ->> '<index-key>' IS NOT NULL ```
tobyhede
approved these changes
Jul 29, 2025
calvinbrewer
approved these changes
Jul 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ProtectJS was generating null search terms and EQL was only checking for the presence of an index key, which would then end up checking if two JSONB null values were equal, which would always return true.
This commit changes checks of the form:
to