Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Could we provide a potentially larger InternalParquetRecordWriter.getDataSize

Open
#3,032 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
data-engineering

Research direction

Locate InternalParquetRecordWriter.getDataSize and trace how Iceberg's rolling file write operation uses its value. Compare the reported size with actual written and buffered data, then define and test a larger, safe size estimate that prevents unexpectedly small files.

Written by the indexing model from the issue text.

Description

The following code currently has getDataSize as an estimated value. The Iceberg rolling file write operation relies on this method, which may result in writing files that are much smaller than expected.

/**
 * @return the total size of data written to the file and buffered in memory
 */
public long getDataSize() {
  return lastRowGroupEndPos + columnStore.getBufferedSize();
}

Could we provide a potentially larger getDataSize? I can't think of any downsides at the moment.

Component(s)

No response

Dominant language
Java
Stars
3.1k
Forks
1.6k
Avg merge
6d 16h
Merged PRs (30d)
36

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/parquet-java

All issues in apache/parquet-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.