amorynan opened a new pull request, #53073:
URL: https://github.com/apache/doris/pull/53073
### What problem does this PR solve?
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
```
Issue Number: close #xxx
Related PR: #xxx
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:
https://github.com/apache/doris-website/pull/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 -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
