-
Notifications
You must be signed in to change notification settings - Fork 409
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
storage: fix block rows not match when filter column is the first non-empty column in the block #9484
Conversation
…-empty column in the block Signed-off-by: Lloyd-Pottiger <yan1579196623@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JaySon-Huang, JinheLin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest |
/retest |
/test pull-integration-test |
1 similar comment
/test pull-integration-test |
fullstack-test2/ddl/rename_table_across_databases.test |
/retest |
What problem does this PR solve?
Issue Number: ref #9472
Problem Summary:
What is changed and how it works?
Try to fix #9472, failed to reproduce the issue. But when the filter column is the first non-empty column in the block, block.rows() = filter_column->size(), but filter_column is not filtered, so the rows may not match.
But filter_column is usually added to the back of the block, so it is kind of weird.
Check List
Tests
Side effects
Documentation
Release note