[Java] Add forward compatibility checks for unrecognized future MetadataVersion
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
We should have no need of these checks in theory, but they present a safeguard should some years in the future it became necessary to increment the MetadataVersion.
**Reporter**: [Bryan Cutler](https://issues.apache.org/jira/browse/ARROW-9545) / @BryanCutler
#### Related issues:
- [[C++] Add forward compatibility checks for unrecognized future MetadataVersion](https://github.com/apache/arrow/issues/25479) (is a clone of)
**Note**: *This issue was originally created as [ARROW-9545](https://issues.apache.org/jira/browse/ARROW-9545). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
Contributor guide
Research direction
The issue names Java MetadataVersion handling but no files, tests, or entry points. Start by locating the Java code that reads or validates MetadataVersion and compare the related C++ issue; done means unrecognized future versions are handled safely with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100