ParquetMetadataConverter.java is too long
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
ParquetMetadataConverter is huge and could benefit from splitting into a few smaller classes with well defined responsibilities.
**Reporter**: [Alex Levenson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alexlevenson) / @isnotinvain
**Assignee**: [Ashish Singh](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=singhashish) / @SinghAsDev
**Note**: *This issue was originally created as [PARQUET-310](https://issues.apache.org/jira/browse/PARQUET-310). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating ParquetMetadataConverter.java and reviewing its current responsibilities. Identify suitable class boundaries and check the existing test coverage before changing structure. Done means the converter is split into smaller classes with clearly defined responsibilities, but the issue provides no specific tests or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100