Le 09/07/2026 à 22:02, Ryan Blue a écrit :
Not quite, because as pointed in another thread, a major version change
in SemVer points to *backwards* incompatible changes, not forwards
incompatible changes.
I would not confuse what is being proposed with SemVer. SemVer is for API
compatibility and it doesn't directly translate to formats. Saying that the
spec or format follows SemVer would be a very different idea.
The previous thread was entitled "[DISCUSS] Moving to SemVer for
parquet-format releases". :-)
In SemVer, a major version bump means my existing code might break because
an API was removed or modified. A minor version bump means that new APIs
were added but existing code will continue to work. So:
- Major version change: existing code may break (this number defines a
compatibility level)
- Other version changes: existing code should not break
The definition for formats is similar:
- Major version change: existing readers may break (this number defines a
compatibility level)
- Other changes: existing readers continue to read correctly
We can decide if we want to have minor versions or patch versions, but the
core idea is the same.
That's a good point. It deserves encoding somewhere, IMHO.
Regards
Antoine.
