Remove deprecated JSON writer #5651
Merged
Conversation
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
tustvold
force-pushed
the
remove-deprecated-json-conversions
branch
from
7b04b10 to
d0d0a6c
Compare
crepererum
approved these changes
Apr 17, 2024
Contributor
Author
|
I intend to hold this until the next major release of arrow, which depending on the outcome of #5654 may be sooner than anticipated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
Closes #.
Rationale for this change
These APIs were deprecated in #5318, have fairly limited test coverage now that the main writer doesn't use them, and have patchy support for nested types. They can now be removed.
What changes are included in this PR?
Are there any user-facing changes?