Skip to content
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

[BugFix] Fix window cumulative algorithm for max/min with string type #55537

Merged
merged 3 commits into from
Feb 5, 2025

Conversation

before-Sunrise
Copy link
Contributor

Why I'm doing:'

Fixes #55532
#54849 support cumulative algorithm for max/min, but forgot to support string type, which is a Specialized template class

we can change be config: pipeline_analytic_enable_removable_cumulative_process to false to bypass this issue temporarily

What I'm doing:

support string type

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.4
    • 3.3
    • 3.2
    • 3.1
    • 3.0

Signed-off-by: before-Sunrise <unclejyj@gmail.com>
Signed-off-by: before-Sunrise <unclejyj@gmail.com>
update(ctx, columns, state, current_frame_last_position);
}
}

void merge(FunctionContext* ctx, const Column* column, AggDataPtr __restrict state, size_t row_num) const override {
DCHECK(column->is_binary());
Slice value = column->get(row_num).get_slice();
Copy link

Choose a reason for hiding this comment

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

The most risky bug in this code is:
Potential out-of-bounds access when accessing null_column->raw_data() if the null column isn't actually available or properly casted.

You can modify the code like this:

if (has_null && columns[1]->is_nullable()) {
    const auto null_column = down_cast<const NullColumn*>(columns[1]);
    const uint8_t* f_data = null_column->raw_data();
    for (size_t i = frame_start; i < frame_end; ++i) {
        if (f_data[i] == 0) {
            update(ctx, columns, state, i);
        }
    }
} else if (!has_null) {
    update_batch_single_state_with_frame(ctx, state, columns, partition_start, partition_end,
                                         frame_start, frame_end);
}

Signed-off-by: before-Sunrise <unclejyj@gmail.com>
Copy link

github-actions bot commented Feb 5, 2025

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

github-actions bot commented Feb 5, 2025

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

github-actions bot commented Feb 5, 2025

[BE Incremental Coverage Report]

pass : 20 / 22 (90.91%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 be/src/exprs/agg/aggregate.h 0 2 00.00% [227, 228]
🔵 be/src/exprs/agg/maxmin.h 20 20 100.00% []

@silverbullet233 silverbullet233 enabled auto-merge (squash) February 5, 2025 10:56
@kangkaisen kangkaisen disabled auto-merge February 5, 2025 10:57
@kangkaisen kangkaisen merged commit f494972 into StarRocks:main Feb 5, 2025
47 checks passed
Copy link

github-actions bot commented Feb 5, 2025

@Mergifyio backport branch-3.4

@github-actions github-actions bot removed the 3.4 label Feb 5, 2025
Copy link

github-actions bot commented Feb 5, 2025

@Mergifyio backport branch-3.3

@github-actions github-actions bot removed the 3.3 label Feb 5, 2025
Copy link
Contributor

mergify bot commented Feb 5, 2025

backport branch-3.4

✅ Backports have been created

Copy link
Contributor

mergify bot commented Feb 5, 2025

backport branch-3.3

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Feb 5, 2025
…#55537)

Signed-off-by: before-Sunrise <unclejyj@gmail.com>
(cherry picked from commit f494972)
mergify bot pushed a commit that referenced this pull request Feb 5, 2025
…#55537)

Signed-off-by: before-Sunrise <unclejyj@gmail.com>
(cherry picked from commit f494972)
wanpengfei-git pushed a commit that referenced this pull request Feb 5, 2025
… (backport #55537) (#55564)

Co-authored-by: before-Sunrise <71162020+before-Sunrise@users.noreply.github.com>
wanpengfei-git pushed a commit that referenced this pull request Feb 5, 2025
… (backport #55537) (#55565)

Co-authored-by: before-Sunrise <71162020+before-Sunrise@users.noreply.github.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.

Min/Max window function generates wrong result when the frame is bounded
3 participants