-
-
Notifications
You must be signed in to change notification settings - Fork 61
feat(eap): Add wildcard search support for array string attributes #7770
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
Open
phacops
wants to merge
4
commits into
master
Choose a base branch
from
pierre/eap-array-wildcard-search
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+200
−6
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6ec8a73
feat(eap): Add wildcard search support for array string attributes
phacops f0776e4
fix(eap): Move array expression building out of attribute_key_to_expr…
phacops 79abb1d
fix(eap): Guard TYPE_ARRAY against non-LIKE operations
phacops 4e69c11
fix(eap): Validate value type for array LIKE comparisons
phacops File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
Incorrect identifier escaping in raw SQL construction
High Severity
The
_build_array_attr_expressionescapes backticks by doubling (replace("", "")`), but the codebase's own `escape_identifier` in `snuba/clickhouse/escaping.py` uses backslash-prefix escaping for both backticks and backslashes (`` → `` \, `\` → `\\`). This inconsistency means backslashes in `attr_name` are not escaped at all. An attribute name containing a backslash followed by content could cause ClickHouse to misparse the backtick-quoted identifier boundary, since `\would be interpreted as an escaped backtick rather than the closing delimiter. Since this flows throughDangerousRawSQLwhich bypasses all safety checks, this could lead to SQL parsing errors or injection.