-
Notifications
You must be signed in to change notification settings - Fork 72
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
feat(clp-s): Unescape string values during ingestion and fix support for search using escape sequences. #622
Open
gibber9809
wants to merge
10
commits into
y-scope:main
Choose a base branch
from
gibber9809:escape-char-fix
base: main
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.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
1717f54
Add utilities for escaping search queries and fix kql escaping behaviour
gibber9809 407ed46
Change archive format to include only unescaped keys and values
gibber9809 0b71b46
Add tests for kql value escaping
gibber9809 8508084
Add tests for more edge cases
gibber9809 1483c35
Address rabbit comments
gibber9809 3abe7b3
Apply suggestions from code review
gibber9809 10307f5
Address code review comments
gibber9809 50653cb
Merge remote-tracking branch 'upstream/main' into escape-char-fix
gibber9809 2042a1e
Remove escaping in ir ingestion path that is unnecessary because of t…
gibber9809 e236e61
Fix array search bug
gibber9809 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 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 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 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 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 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.
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.
I read from the docs that unmatched surrogate pairs are treated as an error without
true
. Do you think we should throw an error here?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.
Right, the behaviour with true specifically is that it will replace any invalid unicode codepoint with a placeholder unicode character. This ensures that this method always returns valid utf-8, but can sometimes modify the original input.
The way I see this is that if a user wants to ingest their data despite it containing some invalid unicode this is really one of the only good ways of doing it automatically.
That said, its possible that some users would prefer failing ingestion so that they get direct feedback that they're producing invalid JSON. I could add a flag for this in this PR, or create a github issue to track this feature to add it later if you want?
Also, for what its worth, I talked to @kirkrodrigues when deciding what to do here and he agreed that the automatic utf-8 fix is probably desirable for large deployments.