Skip to content

branch-4.1: [opt](table-function) Optimize explode with block fast path #60352#62048

Open
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-60352-branch-4.1
Open

branch-4.1: [opt](table-function) Optimize explode with block fast path #60352#62048
github-actions[bot] wants to merge 1 commit intobranch-4.1from
auto-pick-60352-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 2, 2026

Cherry-picked from #60352

- Add a block fast path for explode-like table functions to expand
contiguous nested ranges without per-row get_value()
- Fall back to the original row-wise path when the nested range is
non-contiguous or unsupported
- Add/extend unit tests to cover fast path and fallback cases

Test: ./run-be-ut.sh --run
--filter='TableFunctionOperatorTest.*:UnnestTest.*'

Performance :
Simple Array: 10.1s -> 5.1s
Nested Array: 100.2s -> 20.1s

### What problem does this PR solve?

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:
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 github-actions bot requested a review from yiguolei as a code owner April 2, 2026 09:12
@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?

@dataroaring dataroaring closed this Apr 2, 2026
@dataroaring dataroaring reopened this Apr 2, 2026
@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 85.58% (184/215) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 52.93% (19800/37410)
Line Coverage 36.41% (185991/510784)
Region Coverage 32.72% (144255/440926)
Branch Coverage 33.87% (63276/186812)

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