apache / apache/parquet-java

Use SeekableByteChannel instead of OutputFile/InputFile Classes

Open
#2,519 1 comment 0 reactions 0 assignees View on GitHub
Component: Parquet Priority: Major Type: enhancement
Dominant language
Java
Stars
3.1k
Forks
1.6k
Avg merge
3d 12h
Merged PRs (30d)
33

Description

Use Java NIO SeekableByteChannel for input to reader/writer instead of the current Parquet-only `Output`/`InputFile` Classes

**Reporter**: [David Mollitor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=belugabehr) / @belugabehr
#### Related issues:
- [Parquet without Hadoop dependencies](https://github.com/apache/parquet-java/issues/2473) (relates to)
- [Add Java NIO Avro OutputFile InputFile](https://github.com/apache/parquet-java/issues/2447) (supercedes)

**Note**: *This issue was originally created as [PARQUET-1905](https://issues.apache.org/jira/browse/PARQUET-1905). 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 linked superseding issue, “Add Java NIO Avro OutputFile InputFile,” along with the migration documentation and related issue on removing Hadoop dependencies. Compare the requested SeekableByteChannel input with the current Parquet-only Output/InputFile classes; completion should be defined by the superseding issue and migration guidance.

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
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.