Many classes in parquet-hadoop belong in parquet-column
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
There are a handful of classes, like BlockMetaData and some of the other \*MetaData classes that are currentlyin parquet hadoop but aren't hadoop specific. Which force some other classes (like the row group filter) to also live in parquet-hadoop when they really belong in parquet-column
**Reporter**: [Alex Levenson](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alexlevenson) / @isnotinvain
**Note**: *This issue was originally created as [PARQUET-38](https://issues.apache.org/jira/browse/PARQUET-38). 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 BlockMetaData and the other *MetaData classes in parquet-hadoop, then inspect the row group filter and its module dependencies. The refactor is done when Hadoop-independent metadata and related filtering classes can live in parquet-column without leaving required dependencies behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100