How to avoid numSegmentsPrunedInvalid

Open dang-stripe opened this issue 3 months ago • 1 comments

Based on this error message: https://github.com/apache/pinot/blob/master/pinot-controller/src/main/resources/app/pages/Query.tsx#L401-L406, it seems like queries can fail when segments aren't reloaded after a schema is updated.

How often can this happen in practice and are there ways to avoid it? We have some guidance for users to avoid using select * queries and to explicitly list all columns instead, but it's not actually clear if that would prevent this issue.

We haven't seen this in practice in prod, but wanted to confirm whether the behavior still exists.

cc @Jackie-Jiang @gortiz

Dec 05 '25 00:12 dang-stripe

After #15350 and #15956, the inconsistent window should be minimal, even with select * queries

Dec 11 '25 01:12 Jackie-Jiang