-
Notifications
You must be signed in to change notification settings - Fork 738
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
Support RecordBatch
with zero columns but non zero row count
#1536
Labels
Comments
tustvold
added
the
enhancement
Any new improvement worthy of a entry in the changelog
label
Apr 11, 2022
tustvold
added a commit
to tustvold/arrow-rs
that referenced
this issue
Apr 12, 2022
tustvold
added a commit
to tustvold/arrow-rs
that referenced
this issue
Apr 12, 2022
alamb
pushed a commit
that referenced
this issue
Apr 12, 2022
alamb
changed the title
Create RecordBatch With Non-Zero Row Count But No Columns
Support Apr 15, 2022
RecordBatch
with No Columns but Non-Zero Row Count
alamb
changed the title
Support
Support Apr 15, 2022
RecordBatch
with No Columns but Non-Zero Row CountRecordBatch
with zero columns but non zero row count
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Certain queries may only be interested in the number of rows, and not any actual column data. In theory this could be handled as a projection pushdown that selects no columns, but currently there is no way to create a RecordBatch with no columns and a non-zero row count and so this doesn't work.
Describe the solution you'd like
I would like
RecordBatch
to store therow_count
as a struct member, and allow this to be specified inRecordBatchOptions
Describe alternatives you've considered
We could not make this change
Additional context
This problem can also arise when using Hive style partitioning, where the underlying file data may not contain all columns - apache/datafusion#2000
The text was updated successfully, but these errors were encountered: