Skip to content

branch-4.1: [feature](variant) Add native ColumnVariantV2 execution - #66188

Open
eldenmoon wants to merge 1 commit into
apache:branch-4.1from
eldenmoon:branch-pick-pr-65561-to-branch-4.1
Open

branch-4.1: [feature](variant) Add native ColumnVariantV2 execution#66188
eldenmoon wants to merge 1 commit into
apache:branch-4.1from
eldenmoon:branch-pick-pr-65561-to-branch-4.1

Conversation

@eldenmoon

Copy link
Copy Markdown
Member

cherry-pick #65561

@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@eldenmoon

Copy link
Copy Markdown
Member Author

run buildall

@eldenmoon
eldenmoon marked this pull request as ready for review July 28, 2026 12:54
@eldenmoon
eldenmoon requested a review from yiguolei as a code owner July 28, 2026 12:54
Copilot AI review requested due to automatic review settings July 28, 2026 12:54

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of lines (20,000). Try reducing the number of changed lines and requesting a review from Copilot again.

### What problem does this PR solve?

Issue Number: None

Related PR: apache#65561

Problem Summary: Backport native ColumnVariantV2 execution to branch-4.1. The original change also altered legacy Variant analysis when enable_variant_v2 was disabled. Preserve branch-4.1 legacy GROUP BY, DISTINCT, set-operation, implicit JSON-cast, root comparison, and common-type behavior while enabling canonical Variant V2 execution when the session variable is enabled.

### Release note

Add native Variant V2 execution behind enable_variant_v2 on branch-4.1 while preserving legacy Variant behavior when disabled.

### Check List (For Author)

- Test:
    - Regression test: variant_p0 test_variant_equality_contexts, test_variant_ordering_comparison_error, variant_parse_functions, variant_compute_v2
    - Unit Test: 133 focused FE tests; 228 focused BE tests (1 additional disabled test)
    - Build: ASAN BE build and FE build
- Behavior changed: Yes. Variant V2 execution is enabled only when enable_variant_v2=true; legacy Variant behavior remains unchanged when false.
- Does this need documentation: No
@eldenmoon
eldenmoon force-pushed the branch-pick-pr-65561-to-branch-4.1 branch from cdd9d10 to d93c10a Compare July 28, 2026 12:58
@eldenmoon

Copy link
Copy Markdown
Member Author

run buildall

@eldenmoon
eldenmoon marked this pull request as draft July 28, 2026 12:59
@eldenmoon
eldenmoon marked this pull request as ready for review July 28, 2026 13:00
@eldenmoon

Copy link
Copy Markdown
Member Author

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

Cloud UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 77.58% (1900/2449)
Line Coverage 64.39% (33960/52745)
Region Coverage 64.89% (17506/26980)
Branch Coverage 54.04% (9379/17356)

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage `` 🎉
Increment coverage report
Complete coverage report

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 88.31% (7335/8306) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 57.87% (24101/41649)
Line Coverage 41.92% (240049/572606)
Region Coverage 37.97% (189174/498244)
Branch Coverage 39.22% (85737/218587)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 87.75% (7175/8177) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.56% (29926/40680)
Line Coverage 57.31% (326361/569503)
Region Coverage 54.29% (272086/501171)
Branch Coverage 55.16% (120645/218724)

1 similar comment
@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 87.75% (7175/8177) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.56% (29926/40680)
Line Coverage 57.31% (326361/569503)
Region Coverage 54.29% (272086/501171)
Branch Coverage 55.16% (120645/218724)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants