arrow_output_version option to produce arrow depending on a format version. #17791
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.
This PR introduces a new option, the
arrow_output_version
, which allows us to specify a format version to which we should output our data to. We default to V1.0.This new variable kind of makes the
produce_arrow_string_view
arrow_output_list_view
useless, but I guess that removing them might be slightly controversial, since it might break ppl's scripts. Hence I went with inter-op.https://arrow.apache.org/docs/format/Versioning.html#post-1-0-0-format-versions
Fix: https://github.com/duckdblabs/duckdb-internal/issues/5058