Skip to content

Conversation

Kontinuation
Copy link
Member

@Kontinuation Kontinuation commented Oct 9, 2025

This fixes #186.

The provider ignored the projection indices passed to TableProvider::scan(), so the physical plan schema ([a,b]) did not match the pushed-down logical projection ([b]). This PR implements projection pushdown for RecordBatchReaderProvider and adds a regression test.

@Kontinuation Kontinuation marked this pull request as draft October 9, 2025 04:11
@Kontinuation Kontinuation changed the title Support projection pushdown for RecordBatchReader provider (fixes #186) fix: Support projection pushdown for RecordBatchReader provider (fixes #186) Oct 9, 2025
@Kontinuation Kontinuation marked this pull request as ready for review October 9, 2025 05:34
Copy link
Member

@paleolimbot paleolimbot left a comment

Choose a reason for hiding this comment

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

This one was definitely my fault...thank you for fixing!

@Kontinuation Kontinuation merged commit f79d821 into apache:main Oct 10, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rust/sedona: Projecting a data frame derived from a record batch reder results in a projection error

2 participants