Fix hybrid scan reader state not fully reset for multi-threaded reuse - #22852
Fix hybrid scan reader state not fully reset for multi-threaded reuse#22852Deegue wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds explicit resets in hybrid_scan_reader_impl::reset_internal_state(): sets ChangesHybrid Scan Reader State Reset
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
b969a3a to
3a9b1e6
Compare
|
Thank you for the contribution @Deegue @mhaseeb123 - Do you have time to look at this? |
There was a problem hiding this comment.
Please use the reader->reset_column_selection() API instead. See #22851 (comment)
Description
hybrid_scan_reader_impl::reset_internal_state() was not resetting _output_chunk_produced and the three column selection flags (_is_filter_columns_selected, _is_payload_columns_selected, _is_all_columns_selected). When a reader instance is reused across multiple threads, stale state from a previous read carries over:
This patch adds the missing resets to reset_internal_state().
closes #22851
Checklist