Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Bigquery connector changes #3001
Bigquery connector changes #3001
Changes from 13 commits
00c7614
5d0c8b5
df7ba8b
0972614
0d65aa3
1173696
8536716
5b8fc80
6bd0dcd
29f64e6
cbc4e7c
0a45de8
935ed37
8f60104
c7b1fd2
442f041
21f4adb
d2f1f1b
b872d8b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Why is the extra layer of buffering in
rs.records
needed versus directly bufferingrdr
and proxying to it inNext()
?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.
I tried proxying
rdr
to next but overall it feels lot more complicated than current implementation. There are multiple cases to consider.rdr
will be nil in first next call,rdr
can return next as false if is are no more data or if there is some genuine error(which needs to be handled separately as well). Overall it felt lot easier to just look at the size of the array.Also as of now
ArrowRecordBatch
from bigquery will only return one arrow record but it's better to keep array for any change in underlying impls in future.