Handle special values of floating point statistics
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Based on PARQUET-1251 we have implemented the suggested workaround but it is not complete in all situations.
- We handle the special floating point values at row-group level in parquet-mr but only for the read path. For the write path we still write these values.
- For column indexes we handle these values but only for the write path and not for the read path.
We should implement the workaround for both read and write paths for all cases so we not only handle potentially invalid values but also don't write them to the file.
**Reporter**: [Gabor Szadovszky](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gszadovszky) / @gszadovszky
**Assignee**: [Gabor Szadovszky](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=gszadovszky) / @gszadovszky
**Note**: *This issue was originally created as [PARQUET-2017](https://issues.apache.org/jira/browse/PARQUET-2017). 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 tracing the existing handling of special floating-point values for row-group statistics and column indexes, covering both read and write paths. Confirm the workaround applies in every case, including preventing these values from being written to files, and add or update coverage for the affected paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100