Uh oh!
There was an error while loading. Please reload this page.
[fix](json) Add . after in JSON path to support correct token parsing - #52543
Merged
Conversation
mrhhsg
commented
Jun 30, 2025
MemberAuthor
run buildall |
Thearas
commented
Jun 30, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
16 tasks
doris-robot
commented
Jun 30, 2025
TPC-H: Total hot run time: 34033 ms |
doris-robot
commented
Jun 30, 2025
TPC-DS: Total hot run time: 185028 ms |
mrhhsg
commented
Jun 30, 2025
MemberAuthor
run buildall |
doris-robot
commented
Jun 30, 2025
TPC-H: Total hot run time: 33896 ms |
doris-robot
commented
Jun 30, 2025
TPC-DS: Total hot run time: 185416 ms |
doris-robot
commented
Jun 30, 2025
ClickBench: Total hot run time: 29.96 s |
hello-stephen
commented
Jun 30, 2025
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
mrhhsg
commented
Jul 2, 2025
MemberAuthor
run buildall |
doris-robot
commented
Jul 2, 2025
TPC-H: Total hot run time: 33886 ms |
doris-robot
commented
Jul 2, 2025
TPC-DS: Total hot run time: 183866 ms |
doris-robot
commented
Jul 2, 2025
ClickBench: Total hot run time: 30 s |
hello-stephen
commented
Jul 2, 2025
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
mrhhsg
commented
Jul 2, 2025
MemberAuthor
run buildall |
doris-robot
commented
Jul 2, 2025
TPC-H: Total hot run time: 33801 ms |
doris-robot
commented
Jul 2, 2025
TPC-DS: Total hot run time: 184454 ms |
doris-robot
commented
Jul 2, 2025
ClickBench: Total hot run time: 29.64 s |
hello-stephen
commented
Jul 2, 2025
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
yiguolei
approved these changes
Jul 3, 2025
yiguolei
approved these changes
Jul 3, 2025
Mryange
approved these changes
Jul 3, 2025
yiguolei pushed a commit
that referenced
this pull request
Jul 3, 2025
…#52543) (#52544) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
mrhhsg added a commit
to mrhhsg/doris
that referenced
this pull request
Jul 3, 2025
…apache#52543) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
16 tasks
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jul 4, 2025
…apache#52543) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jul 4, 2025
…apache#52543) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
koarz pushed a commit
to koarz/doris
that referenced
this pull request
Jul 4, 2025
…apache#52543) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
dataroaring pushed a commit
that referenced
this pull request
Jul 4, 2025
…#52543) (#52744) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior. ### What problem does this PR solve? pick #52543 Issue Number: close #xxx Related PR: #52543 Problem Summary: ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into -->
seawinde pushed a commit
to seawinde/doris
that referenced
this pull request
Jul 4, 2025
…apache#52543) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
mrhhsg added a commit
to mrhhsg/doris
that referenced
this pull request
Jul 4, 2025
…apache#52543) (apache#52744) Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior. ### What problem does this PR solve? pick apache#52543 Issue Number: close #xxx Related PR: apache#52543 Problem Summary: ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into -->
morrySnow pushed a commit
that referenced
this pull request
Jul 8, 2025
Closed
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
Sign up for freeto 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.
Boost tokenizer requires explicit "." after "$" to correctly extract JSON path tokens. Without this, expressions like "$[0].key" cannot be properly split, causing issues in downstream logic. This commit ensures a "." is automatically added after "$" to maintain consistent token parsing behavior.
What problem does this PR solve?
before:
after:
Problem Summary:
Release note
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)