apache/pinot

Deep Stack Trace from Long Min/Max Column Values

Open

#17378 opened on Dec 16, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (4,937 stars) (1,234 forks)batch import
help wanted

Description

If a column has a very long value, and it ends up being either the min or max, then it gets stored in the segment metadata file.

When the properties reader is used to read such a file, we can have a very deep recursion call stack due to some regex matching.

Contributor guide

Tech stack
java
Domain
database
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaUnderstanding of segment metadata
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the properties reader in the segment metadata file to understand how long min/max values cause deep recursion due to regex matching. Look at the stack trace to identify the specific regex pattern causing the issue. Consider limiting the length of stored values or optimizing the regex to avoid deep recursion.