refactor(arrow): fourth increment of the Record -> RecordBatch migration #486
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.
Rationale for this change
Rename the Record interface to RecordBatch for clarity, since Record commonly means a single row but this type represents a batch of rows.
In addition, some method names such as NewRecord have been changed to NewRecordBatch, but the old methods still exist as wrappers around the newly named methods to maintain backward compatibility.
What changes are included in this PR?
The following packages now use RecordBatch instead of Record:
arrow/ipc
arrow/flight
arrow/flight/flightsql
arrow/internal/flight_integration
arrow/array
In addition:
Are these changes tested?
All affected packages build successfully and core tests pass. Some tests requiring external dependencies were skipped.
This is the fourth increment of the Record → RecordBatch migration.