Add integration tests for all `parquet-testing` files
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- java
- Domain
- testing-qa
Research direction
Start with parquet-hadoop/src/test/java/org/apache/parquet/hadoop/InterOpTester.java and review how it downloads and tests selected parquet-testing files. Run the existing interoperability tests, then map every file in the pinned parquet-testing revision into valid or invalid cases. Done means all files are independently reported, valid files read successfully, invalid files fail as expected, and unclassified files fail the test.
Written by the indexing model from the issue text.
Description
Feature request
Add integration tests that run against every Parquet file in the apache/parquet-testing repository.
Problem
parquet-java currently tests only selected files from parquet-testing. As a result, new interoperability fixtures are not automatically tested, and compatibility regressions may go undetected.
There are already several parquet-java issues involving files from parquet-testing.
Proposed solution
Add integration tests that classify files into two groups:
- Valid files: must open successfully and allow all row groups and columns to be read.
- Invalid files: must fail during footer parsing or record decoding with an expected exception.
InterOpTester already supports downloading individual files from parquet-testing. This feature would extend that approach to provide repository-wide coverage.
Acceptance criteria
- Every Parquet file in the pinned revision is classified.
- All valid files are read successfully.
- All invalid files fail as expected.
- Each file is reported as an independent test.
- Unclassified files cause the test to fail.
- Exclusions require an explicit entry linked to a tracking issue.
Related issues
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 28
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/parquet-java
-
Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/parquet-java#3792 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/parquet-java#3767 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/parquet-java#3695 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/parquet-java#3667 ·
-
Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
apache/parquet-java#3587 ·
All issues in apache/parquet-java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·