-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
refactor: remove uses of arrow_buffer
& arrow_array
and use reexport in arrow instead
#14503
Conversation
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.
Thank you so much @Chen-Yuan-Lai
I also took the liberty of removing a few more uses of arrow_buffer and removed it from the Cargo.toml files and pushed that change to this PR
It turns out OffsetBufferBuilder
is still used in some places so I made an upstream PR in arrow-rs to help:
Any chance you are willing to do the same thing for arrow-array?
@@ -52,7 +52,6 @@ apache-avro = { version = "0.17", default-features = false, features = [ | |||
], optional = true } | |||
arrow = { workspace = true } | |||
arrow-array = { workspace = true } | |||
arrow-buffer = { workspace = true } |
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 also removed the dependency directly from Cargo.toml
Sure : ) |
To be clear, I suggest we do this in a separate PR |
I plan to merge this PR when the CI checks pass |
Thanks again @Chen-Yuan-Lai |
Which issue does this PR close?
Closes #14115.
Rationale for this change
As #14115 (comment) says, we should use reexport in arrow as much as possible.
What changes are included in this PR?
Are these changes tested?
use arrow_buffer:: xxx
->use arrow::buffer::xxx
use arrow_array:: xxx
->use arrow::array::xxx
I leave some imports as it is when those modules weren't reexported in arrow
Are there any user-facing changes?