airborne12 opened a new pull request, #69250:
URL: https://github.com/apache/doris/pull/69250
### What problem does this PR solve?
Issue Number: None
Related PR: #69248 (source), #69244
Problem Summary: Backport the regression fixture fix from #69248. Fuzzy
sessions can enable Variant document mode, making the fixture's INSERT fail
when its `parse_to_variant()` values use the non-document representation. Pin
`default_variant_enable_doc_mode=false` before creating the table.
Source commit: `654327b82d2c4976625ee55a3a94062c6dd7866d`, cherry-picked
with `-x`. The source PR is currently open; this backport uses that pinned head.
#### Hunk audit
| Source file | Disposition |
| --- | --- |
| `regression-test/suites/search/test_search_segment_document_ids.groovy` |
Ported verbatim; its complete postimage matches the source commit. |
`git range-diff` shows only the added cherry-pick provenance line in the
commit message. There are no code adaptations.
### Release note
None
### Check List (For Author)
- Test
- [x] Regression test: `./run-regression-test.sh --run --conf
<local-config> -d search -s test_search_segment_document_ids` passed in this
branch-4.2 worktree with JDBC
`sessionVariables=default_variant_enable_doc_mode=true`: 1 suite, 0 failures,
all 16 V2/SNII golden checks executed. Expected output is unchanged.
- [x] Manual test: the master source suite was verified RED before the
one-line fix and GREEN afterward under the same forced default. Both worktrees
used isolated copies of the existing branch-4.2 ASAN FE/BE runtime built for
`9c2283cfe1e53f1bd6b7473fa3168125ddf1c359`. No ASAN report appeared in the
focused backport run. No new kernel build or BE/FE unit test run was needed for
this Groovy-only change.
- Behavior changed:
- [x] No production behavior changes.
- Does this need documentation?
- [x] No.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
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]
