Avoid Hadoop interfaces and classes in codecs
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Currently the codecs implemented by Parquet implement the Hadoop Configurable and CompressionCodec interfaces. As part of the effort to decouple from Hadoop there need to be alternatives to these Hadoop implementations such that users are not forced to load Hadoop classes for this purpose at runtime.
**Reporter**: [Atour Mousavi Gourabi](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=amousavigourabi) / @amousavigourabi
#### Related issues:
- [Parquet without Hadoop dependencies](https://github.com/apache/parquet-java/issues/2473) (is related to)
- [Add interface layer between Parquet and Hadoop Configuration](https://github.com/apache/parquet-java/issues/2812) (is related to)
**Note**: *This issue was originally created as [PARQUET-2353](https://issues.apache.org/jira/browse/PARQUET-2353). 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 reading the related issues on removing Hadoop dependencies and adding an interface layer between Parquet and Hadoop Configuration, then inspect the codec implementations that currently use Hadoop Configurable and CompressionCodec. Done means users can use the codecs without loading Hadoop classes at runtime, with the replacement interfaces and compatibility behavior defined by that surrounding work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100