Deep Stack Trace from Long Min/Max Column Values

[ankitsultana]

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.

[bluemeaford]

Thanks for reporting this — it sounds like a metadata parsing issue rather than a query/runtime problem.

To help narrow it down, could you share:
1. Pinot version(s) affected
2. Whether this occurs only for STRING columns (min/max values), and roughly how large those values are
3. A snippet of the stack trace showing where the regex parsing happens (class/method), or the specific metadata property being read
4. Whether this happens during segment load/startup vs query-time metadata access

If this is caused by regex backtracking on very large metadata values, a possible mitigation might be limiting or truncating stored min/max values, or switching to a non-regex parsing approach for properties. Happy to help further if more details are available.