parquet-hadoop tests to work with hadoop 3.4.0
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Test runs of parquet-hadoop with `-Dhadoop.version=3.4.0` fail because there's a logback jar on the classpath, which screws things up (mostly seemingly because it suddenly logs at debug)
HADOOP-19084 should have fixed this, as it explicitly excludes the export. clearly not. created HADOOP-19153 as a followup.
For now, all parquet needs is to exclude logback as a hadoop-common dependency. I'll be extra cautious and get rid of all log dependencies.
**Reporter**: [Steve Loughran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stevel@apache.org) / @steveloughran
#### Related issues:
- [hadoop-common still exports logback as a transitive dependency](https://issues.apache.org/jira/browse/HADOOP-19153) (relates to)
#### PRs and other links:
- [GitHub Pull Request #1321](https://github.com/apache/parquet-mr/pull/1321)
**Note**: *This issue was originally created as [PARQUET-2459](https://issues.apache.org/jira/browse/PARQUET-2459). 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 with the parquet-hadoop test setup and dependency configuration, then run the tests with -Dhadoop.version=3.4.0 to reproduce the classpath problem. Check that the Hadoop dependency no longer brings the unwanted logging jars into the test classpath and that the tests pass; HADOOP-19153 and pull request #1321 provide context for work already underway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100