-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature](table-function)support posexplode table function #43221
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clang-tidy made some suggestions
run buildall |
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 43222 ms
|
TPC-DS: Total hot run time: 195819 ms
|
ClickBench: Total hot run time: 32.66 s
|
run buildall |
TeamCity be ut coverage result: |
fe/fe-core/src/main/java/org/apache/doris/catalog/BuiltinTableGeneratingFunctions.java
Outdated
Show resolved
Hide resolved
TPC-H: Total hot run time: 41517 ms
|
TPC-DS: Total hot run time: 195578 ms
|
ClickBench: Total hot run time: 32.12 s
|
run buildall |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clang-tidy made some suggestions
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 41906 ms
|
TPC-DS: Total hot run time: 196646 ms
|
ClickBench: Total hot run time: 32.53 s
|
run buildall |
regression-test/data/nereids_p0/sql_functions/table_function/pose_explode.out
Outdated
Show resolved
Hide resolved
...src/main/java/org/apache/doris/nereids/trees/expressions/functions/generator/PosExplode.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/apache/doris/nereids/trees/expressions/functions/generator/PosExplode.java
Outdated
Show resolved
Hide resolved
TPC-H: Total hot run time: 41231 ms
|
TPC-DS: Total hot run time: 195665 ms
|
ClickBench: Total hot run time: 32.66 s
|
run buildall |
TPC-H: Total hot run time: 41181 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 191516 ms
|
ClickBench: Total hot run time: 31.67 s
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
### What problem does this PR solve? <!-- You need to clearly describe your PR in this part: 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 this function was added. 4. Which codes were refactored and why this part of the code was refactored. 5. Which functions were optimized and what is the difference before and after the optimization. The description of the PR needs to enable reviewers to quickly and clearly understand the logic of the code modification. --> <!-- If there are related issues, please fill in the issue number. - If you want the issue to be closed after the PR is merged, please use "close #12345". Otherwise, use "ref #12345" --> Issue Number: close #xxx <!-- If this PR is followup a preivous PR, for example, fix the bug that introduced by a related PR, link the PR here --> Related PR: #xxx Problem Summary: support posexplode table function doc: apache/doris-website#1283
) <!-- You need to clearly describe your PR in this part: 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 this function was added. 4. Which codes were refactored and why this part of the code was refactored. 5. Which functions were optimized and what is the difference before and after the optimization. The description of the PR needs to enable reviewers to quickly and clearly understand the logic of the code modification. --> <!-- If there are related issues, please fill in the issue number. - If you want the issue to be closed after the PR is merged, please use "close apache#12345". Otherwise, use "ref apache#12345" --> Issue Number: close #xxx <!-- If this PR is followup a preivous PR, for example, fix the bug that introduced by a related PR, link the PR here --> Related PR: #xxx Problem Summary: support posexplode table function doc: apache/doris-website#1283
…#43221 (#45782) Cherry-picked from #43221 Co-authored-by: zhangstar333 <[email protected]>
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
support posexplode table function
doc: apache/doris-website#1283
Check List (For Committer)
Test
Behavior changed:
Does this need documentation?
Release note
None
Check List (For Reviewer who merge this PR)