Skip to content

branch-3.1: [Bug](function) fix wrong result of hll_to_base64 #51831 #51919

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.

Sign up for GitHub

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

Jump to bottom
Merged
morrySnow merged 1 commit into from
Jun 19, 2025
Merged

branch-3.1: [Bug](function) fix wrong result of hll_to_base64 #51831 #51919

morrySnow merged 1 commit into from
Jun 19, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jun 19, 2025

Cherry-picked from #51831

@BiteTheDDDDt
[Bug](function) fix wrong result of hll_to_base64 (#51831)
255ba69 
W20250617 18:57:43.532994 1586470 status.h:435] meet error status:
[RUNTIME_ERROR]hll_from_base64 decode failed: base64:
AuQDAAAMAAMtAAFGAAN0AAOYAAG8AAXKAALaAAHiAALqAALyAAQoAQMrAQFVAQJuAQF3AQR6AQR/
@github-actions github-actions bot requested a review from morrySnow as a code owner June 19, 2025 05:08
@Thearas
Copy link
Contributor

Thearas commented Jun 19, 2025

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 reopened this Jun 19, 2025
@Thearas
Copy link
Contributor

Thearas commented Jun 19, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented Jun 19, 2025

BE UT Coverage Report

Increment line coverage 0.00% (0/2) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 41.18% (10896/26462)
Line Coverage 31.99% (93199/291320)
Region Coverage 31.07% (48086/154757)
Branch Coverage 27.54% (24632/89446)

@morrySnow morrySnow merged commit ee00251 into branch-3.1 Jun 19, 2025
21 of 24 checks passed
@morrySnow morrySnow deleted the auto-pick-51831-branch-3.1 branch June 19, 2025 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnow morrySnow morrySnow approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@Thearas @hello-stephen @morrySnow @dataroaring @BiteTheDDDDt