Skip to content

[Feature](func) Support function QUANTILE_STATE_TO/FROM_BASE64#59664

Merged
yiguolei merged 1 commit intoapache:masterfrom
linrrzqqq:qts-mst
Jan 12, 2026
Merged

[Feature](func) Support function QUANTILE_STATE_TO/FROM_BASE64#59664
yiguolei merged 1 commit intoapache:masterfrom
linrrzqqq:qts-mst

Conversation

@linrrzqqq
Copy link
Copy Markdown
Contributor

@linrrzqqq linrrzqqq commented Jan 8, 2026

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #59607

Problem Summary:

Release note

doc: apache/doris-website#3279
None

Check List (For Author)

  • Test

    • 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
  • Behavior changed:

  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@linrrzqqq linrrzqqq requested a review from zclllyybb as a code owner January 8, 2026 02:58
@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Jan 8, 2026

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?

@linrrzqqq
Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 90.48% (19/21) 🎉
Increment coverage report
Complete coverage report

2 similar comments
@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 90.48% (19/21) 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 90.48% (19/21) 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 42.53% (37/87) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.01% (18974/35794)
Line Coverage 39.08% (175836/449934)
Region Coverage 33.68% (136247/404516)
Branch Coverage 34.67% (58835/169708)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 95.40% (83/87) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.99% (25867/34960)
Line Coverage 61.39% (275234/448331)
Region Coverage 56.33% (230171/408625)
Branch Coverage 58.15% (98975/170212)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 95.40% (83/87) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.92% (25842/34960)
Line Coverage 61.27% (274673/448331)
Region Coverage 56.18% (229560/408625)
Branch Coverage 58.03% (98768/170212)

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 90.48% (19/21) 🎉
Increment coverage report
Complete coverage report

Copy link
Copy Markdown
Contributor

@HappenLee HappenLee left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Jan 9, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 9, 2026

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 9, 2026

PR approved by anyone and no changes requested.

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 95.40% (83/87) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 73.92% (25841/34960)
Line Coverage 61.27% (274678/448331)
Region Coverage 56.17% (229545/408625)
Branch Coverage 58.03% (98767/170212)

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 71.43% (15/21) 🎉
Increment coverage report
Complete coverage report

@yiguolei yiguolei merged commit fea543c into apache:master Jan 12, 2026
33 of 34 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 12, 2026
### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #59607 

Problem Summary:

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [x] 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 -->
yiguolei pushed a commit that referenced this pull request Jan 13, 2026
…ASE64 #59664 (#59746)

Cherry-picked from #59664

Co-authored-by: linrrarity <linzhenqi@selectdb.com>
@linrrzqqq linrrzqqq deleted the qts-mst branch January 13, 2026 07:25
zzzxl1993 pushed a commit to zzzxl1993/doris that referenced this pull request Jan 13, 2026
…e#59664)

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: apache#59607 

Problem Summary:

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [x] 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 -->
feiniaofeiafei pushed a commit to feiniaofeiafei/doris that referenced this pull request Jan 20, 2026
ybtsdst pushed a commit to ybtsdst/doris that referenced this pull request Feb 27, 2026
…ASE64 apache#59664 (apache#59746)

Cherry-picked from apache#59664

Co-authored-by: linrrarity <linzhenqi@selectdb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants