Le 10/06/2026 à 13:14, Andrew Lamb a écrit :
> The problem I think we're trying to solve is to make it easier and safer
for users to enable modern features that produce more optimized and more
efficient Parquet files.
I agree
I agree with the "non-trivial consensus" problem, and that's the point
of calendar-based presets: they eschew the need for "non-trivial
consensus" as they are based on actual adoption. :-)
To be clear I am not opposed to presets (or some other schemes to make
adoption clearer)
In fact, as perhaps you are hinting at, the implementation status page[1]
already has a table with yearly adoption ("Minimum Version for Read Support
by Year"). Perhaps that is enough
I don't understand what this table means or how it's supposed to be
utilized. What is a "2025 Feature"? Why does Arrow C++ not support "2025
Features"?
In any case, this does not seem to be solving the problem of "as a user,
how do I enable features safely".
Regards
Antoine.
