[doc](json load) default behavior change #2874
Merged
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
Merged
16 tasks
liaoxin01
reviewed
Sep 28, 2025
| 3. Routine Load：参数通过 `PROPERTIES` 指定，如：`PROPERTIES("jsonpaths"="$.data")` | ||
| 4. TVF：参数通过 TVF 语句指定，如：`S3("jsonpaths"="$.data")` | ||
| 5. 如果需要将 JSON 文件中根节点的 JSON 对象导入，jsonpaths 需要指定为$.，如：`PROPERTIES("jsonpaths"="$.")` | ||
| 6. read_json_by_line默认为true指的是如果导入时不指定strip_outer_array和read_json_by_line任何一个, 那么read_json_by_line为true. |
dataroaring
pushed a commit
to apache/doris
that referenced
this pull request
Sep 28, 2025
…son_by_line (#55861) ### What problem does this PR solve? Issue Number: close #xxx Related PR: [doc-2874](apache/doris-website#2874) Problem Summary: For the read_json_by_line and strip_outer_array parameters, considering that the first parameter will gradually be deprecated in the future, and some users may forget to specify these two parameters when importing JSON files, I will modify the default behavior of these two parameters: if the user does not specify values for these two parameters, the default setting for read_json_by_line will be true. Behavior patterns after this PR: 1、In scenarios such as S3 load, since read_json_by_line is not only related to importing JSON formats but also serves as the switch for streaming JSON file reading, it will be hardcoded to true (thus, JSON formats requiring this parameter to be false are not supported in such environments). 2、In scenarios such as Stream Load, users have absolute freedom to specify any combination of parameter values (though typically we do not expect users to actively set either to false). ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [x] 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: - [x] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [x] 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 -->
github-actions bot
pushed a commit
to apache/doris
that referenced
this pull request
Sep 28, 2025
…son_by_line (#55861) ### What problem does this PR solve? Issue Number: close #xxx Related PR: [doc-2874](apache/doris-website#2874) Problem Summary: For the read_json_by_line and strip_outer_array parameters, considering that the first parameter will gradually be deprecated in the future, and some users may forget to specify these two parameters when importing JSON files, I will modify the default behavior of these two parameters: if the user does not specify values for these two parameters, the default setting for read_json_by_line will be true. Behavior patterns after this PR: 1、In scenarios such as S3 load, since read_json_by_line is not only related to importing JSON formats but also serves as the switch for streaming JSON file reading, it will be hardcoded to true (thus, JSON formats requiring this parameter to be false are not supported in such environments). 2、In scenarios such as Stream Load, users have absolute freedom to specify any combination of parameter values (though typically we do not expect users to actively set either to false). ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [x] 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: - [x] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [x] 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 -->
github-actions bot
pushed a commit
to apache/doris
that referenced
this pull request
Oct 9, 2025
…son_by_line (#55861) ### What problem does this PR solve? Issue Number: close #xxx Related PR: [doc-2874](apache/doris-website#2874) Problem Summary: For the read_json_by_line and strip_outer_array parameters, considering that the first parameter will gradually be deprecated in the future, and some users may forget to specify these two parameters when importing JSON files, I will modify the default behavior of these two parameters: if the user does not specify values for these two parameters, the default setting for read_json_by_line will be true. Behavior patterns after this PR: 1、In scenarios such as S3 load, since read_json_by_line is not only related to importing JSON formats but also serves as the switch for streaming JSON file reading, it will be hardcoded to true (thus, JSON formats requiring this parameter to be false are not supported in such environments). 2、In scenarios such as Stream Load, users have absolute freedom to specify any combination of parameter values (though typically we do not expect users to actively set either to false). ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [x] 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: - [x] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [x] 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 -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Versions
Languages
Docs Checklist