[
https://issues.apache.org/jira/browse/ARROW-12203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315624#comment-17315624
]
Joris Van den Bossche commented on ARROW-12203:
-----------------------------------------------
I was trying to argue that IMO we don't need to use a pseudo-version like
"1.9", but can rather use the actual version like "2.4". Yes, "2.0" is lower
than "2.4", but if we clearly say that "2.0" means the "latest 2.x", then I
think that is fine.
But anyway, that's only a naming discussion, and both ways to name the version
have pros and cons. The main discussion point is whether we need such an
additional version number to have more fine-grained control over which features
are used. If that makes it easier to make "1.9"/"2.4" the default, then I think
that's a good idea.
> [C++][Python] Switch default Parquet version to 2.0
> ---------------------------------------------------
>
> Key: ARROW-12203
> URL: https://issues.apache.org/jira/browse/ARROW-12203
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++, Python
> Reporter: Antoine Pitrou
> Priority: Major
> Fix For: 4.0.0
>
>
> Currently, Parquet write APIs default to maximum-compatibility Parquet
> version "1.0", which disables some logical types such as UINT32. We may want
> to switch the default to "2.0" instead, to allow faithful representation of
> more types.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
