ConsecutiveChunkList's length field should be long instead of int
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.6k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 33
Description
Hi, we encountered some read failure for large column chunk(size > Int.MaxValue). After some debugging, the buggy code is that ConsecutiveChunkList's length field is int, and it overflows when the uncompressed size of one ColumnChunk is large than Int.MaxValue.
Below is the exception stack:

The column size is some what:

**Reporter**: [YE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=advancedxy) / @advancedxy
**Assignee**: [YE](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=advancedxy) / @advancedxy
#### Original Issue Attachments:
- [image-2021-05-10-17-12-00-083.png](https://issues.apache.org/jira/secure/attachment/13025233/image-2021-05-10-17-12-00-083.png)
- [image-2021-05-10-17-14-45-401.png](https://issues.apache.org/jira/secure/attachment/13025232/image-2021-05-10-17-14-45-401.png)
**Note**: *This issue was originally created as [PARQUET-2045](https://issues.apache.org/jira/browse/PARQUET-2045). 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
Locate ConsecutiveChunkList and trace how its length field is used while reading a large column chunk. Reproduce the reported failure with an uncompressed size above Int.MaxValue, then verify that the length is handled without overflow and that the read succeeds.
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
- 30/100