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

Discussion around storing SUM as a optional metadata field.

Open
#596 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active

Research direction

Start by reviewing the existing Parquet metadata fields and optional bloom-filter handling described in the issue. Define how optional SUM metadata would be represented and how overflow and SUM/AVG pre-aggregation should work. Done means the format design and its trade-offs are agreed.

Written by the indexing model from the issue text.

Description

Type: enhancement
Describe the enhancement requested

Currently parquet only stores fields for predicate pushdown for scan pruning, but we can also keep sum in metadata field, while this won't help in predicate pushdown, but it can act as a pre-aggregation for sum and avg queries.

While this may be challenging and bit complex because we would need to handle sum/overflow etc. But this can be optional just like bloom filters and would be helpful for many usecases. And shouldn't have much of a overhead due to it being a stateless operation.

Dominant language
Thrift
Stars
2.6k
Forks
509
Avg merge
5d 21h
Merged PRs (30d)
2

Getting set up

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-format

All issues in apache/parquet-format

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.