Remove pyarrow-legacy engine from parquet API#8835
Merged
Conversation
Member
|
Why don't we merge this after our next release? Gives a little over a month of deprecation warning in effect, and it hasn't been the default engine for a while. |
3 tasks
bryanwweber
reviewed
Mar 25, 2022
Member
|
I've merged this with main and pushed a small fixup - I believe this should be good to merge once tests pass. Thanks @rjzamora! edit: looks like there are some test failures, will fix |
Member
|
Errors are unrelated, merging. Thanks @rjzamora! |
Member
Author
|
Thanks for taking care of this @jcrist ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Removes parquet "pyarrow-legacy" engine. This is a follow-up to #8758 and the final step in #8243
I'm not sure how long we want to wait from the date #8758 to release this, but doing so will certainly help with maintenance a bit :)