Skip to content

branch-2.0: [Bug](function) fix wrong result when case when have more than 256 conditions and the… #47179 #47395

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
BiteTheDDDDt merged 2 commits into from
Feb 14, 2025
Merged

branch-2.0: [Bug](function) fix wrong result when case when have more than 256 conditions and the… #47179 #47395

BiteTheDDDDt merged 2 commits into from
Feb 14, 2025

Conversation

@BiteTheDDDDt
Copy link
Contributor

@BiteTheDDDDt BiteTheDDDDt commented Jan 24, 2025

Cherry-picked from #47179

@BiteTheDDDDt
[Bug](function) fix wrong result when case when have more than 256 co…
0aa76f9 
…nditions and the… (apache#47179)

### What problem does this PR solve?
fix wrong result when case when have more than 256 conditions and then
column is not nullable
### 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:
    - [x] No.
    - [ ] Yes. <!-- Explain the behavior change -->

- Does this need documentation?
    - [x] 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 -->
@Thearas
Copy link
Contributor

Thearas commented Jan 24, 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?

@BiteTheDDDDt BiteTheDDDDt changed the base branch from master to branch-2.0 January 24, 2025 03:50
@BiteTheDDDDt
Copy link
Contributor Author

BiteTheDDDDt commented Jan 24, 2025

run buildall

4 similar comments
@BiteTheDDDDt
Copy link
Contributor Author

BiteTheDDDDt commented Jan 27, 2025

run buildall

@BiteTheDDDDt
Copy link
Contributor Author

BiteTheDDDDt commented Feb 5, 2025

run buildall

@BiteTheDDDDt
Copy link
Contributor Author

BiteTheDDDDt commented Feb 10, 2025

run buildall

@BiteTheDDDDt
Copy link
Contributor Author

BiteTheDDDDt commented Feb 14, 2025

run buildall

@BiteTheDDDDt
Copy link
Contributor Author

BiteTheDDDDt commented Feb 14, 2025

run buildall

@BiteTheDDDDt BiteTheDDDDt merged commit 557edd3 into apache:branch-2.0 Feb 14, 2025
18 of 21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gavinchou gavinchou Awaiting requested review from gavinchou

@dataroaring dataroaring Awaiting requested review from dataroaring

Assignees

No one assigned

Labels

kind/test

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@BiteTheDDDDt @Thearas