branch-3.1: [fix](variant) fix the reading core caused by inserting nested column and scalar column in variant sub-column #53083#53977
Merged
morrySnow merged 11 commits intoapache:branch-3.1from Jul 31, 2025
Conversation
… and scalar column in variant sub-column (apache#53083) this pr main fix the problem which if we create table with ```variant_enable_flatten_nested``` then insert variant data: ```'{"nested":{"a":"1"}}``` and ```'{"nested":[{"a":1,"c":1.1},{"b":"1"}]}'``` we will meet core for reading so we should forbid this table property and for old data we insert different structure data will meet some error like this: ``` mysql> insert into vs values (2, '{"nested":{"a":"1"}}'); Query OK, 1 row affected (0.22 sec) {'label':'label_165a8209698c4391_988c6532615017c4', 'status':'VISIBLE', 'txnId':'1011'} mysql> insert into vs values (1, '{"nested":[{"a":1,"c":1.1},{"b":"1"}]}'); ERROR 1105 (HY000): errCode = 2, detailMessage = (10.16.10.6)[INTERNAL_ERROR]tablet 1752145213719 failed on majority backends: [DATA_QUALITY_ERROR]PStatus: (10.16.10.6)[DATA_QUALITY_ERROR]Ambiguous paths: v.nested.a vs v.nested.a with different nested part true vs false ```
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
morrySnow
changed the title
Contributor
Author
|
run buildall |
Contributor
Author
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
Author
|
run buildall |
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 32385 ms |
TPC-DS: Total hot run time: 196553 ms |
ClickBench: Total hot run time: 29.23 s |
Contributor
Author
|
run buildall |
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 32537 ms |
TPC-DS: Total hot run time: 189568 ms |
ClickBench: Total hot run time: 28.2 s |
Contributor
Author
|
run buildall |
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
Author
|
run buildall |
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 32884 ms |
TPC-DS: Total hot run time: 197213 ms |
ClickBench: Total hot run time: 29.15 s |
Contributor
Author
|
run buildall |
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 32705 ms |
Contributor
FE UT Coverage ReportIncrement line coverage |
TPC-DS: Total hot run time: 196261 ms |
ClickBench: Total hot run time: 29.25 s |
morrySnow
approved these changes
Jul 31, 2025
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
backport: #53083