parquet-avro logical type support broke ability to use avro reflection with generics.
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Impacts 1.9.0 and 1.8.2.
Assuming the fieldClass is a concrete class (which it is for all of the logical types) is an incorrect assumption when generics are used.
Statistics {
T field1
T field2
}
SetStatistics extends Statistics> {}
Solution is to check if the fieldClass is abstract/interface/raw object.
**Reporter**: [Evan McClain](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aeroevan) / @aeroevan
**Assignee**: [Evan McClain](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aeroevan) / @aeroevan
#### Original Issue Attachments:
- [0001-Do-not-pass-knownClass-if-it-is-abstract-interface.patch](https://issues.apache.org/jira/secure/attachment/12850491/0001-Do-not-pass-knownClass-if-it-is-abstract-interface.patch)
**Note**: *This issue was originally created as [PARQUET-856](https://issues.apache.org/jira/browse/PARQUET-856). 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
Use the Statistics and SetStatistics extends Statistics> examples to reproduce the Avro reflection failure. Inspect the parquet-avro logical type handling around fieldClass and compare it with the attached patch; done means generic reflection works without passing an abstract, interface, or raw Object class as the known class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100