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

Fix bounds check in MultiChannelGroupByHash and BigintGroupByHash #12597

Merged
merged 1 commit into from
May 31, 2022

Conversation

sopel39
Copy link
Member

@sopel39 sopel39 commented May 30, 2022

There's an off-by-one error in the check that
can cause a failure when the page is empty

Description

Is this change a fix, improvement, new feature, refactoring, or other?

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

How would you describe this change to a non-technical end user or system administrator?

Related issues, pull requests, and links

Documentation

( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

There's an off-by-one error in the check that
can cause a failure when the page is empty
@cla-bot cla-bot bot added the cla-signed label May 30, 2022
@sopel39 sopel39 marked this pull request as ready for review May 30, 2022 20:25
Copy link
Member

@losipiuk losipiuk left a comment

Choose a reason for hiding this comment

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

LGTM. Is it testable?

@sopel39
Copy link
Member Author

sopel39 commented May 31, 2022

LGTM. Is it testable?

Probably. IMO it needs a cleanup of TestGroupByHash. Will try to do so when I have time

@sopel39 sopel39 merged commit d9bb461 into trinodb:master May 31, 2022
@sopel39 sopel39 deleted the ks/fix_check branch May 31, 2022 06:57
@github-actions github-actions bot added this to the 383 milestone May 31, 2022
@colebow
Copy link
Member

colebow commented May 31, 2022

Do we want to include a release note for this?

@sopel39
Copy link
Member Author

sopel39 commented May 31, 2022

Do we want to include a release note for this?

No. This fixed bug in non-released version

v-jizhang added a commit to v-jizhang/presto that referenced this pull request Jun 9, 2022
Cherry-pick of trinodb/trino#12597

There's an off-by-one error in the check that
can cause a failure when the page is empty.

Co-authored-by: Karol Sobczak <[email protected]>
highker pushed a commit to prestodb/presto that referenced this pull request Aug 3, 2022
Cherry-pick of trinodb/trino#12597

There's an off-by-one error in the check that
can cause a failure when the page is empty.

Co-authored-by: Karol Sobczak <[email protected]>
shrinidhijoshi pushed a commit to shrinidhijoshi/presto that referenced this pull request Sep 7, 2022
Cherry-pick of trinodb/trino#12597

There's an off-by-one error in the check that
can cause a failure when the page is empty.

Co-authored-by: Karol Sobczak <[email protected]>
Copy link
Contributor

@aaneja aaneja left a comment

Choose a reason for hiding this comment

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

Accidental review, please ignore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

5 participants