In the docs at https://docs.pinot.apache.org/users/tutorials/schema-evolution#update-the-schema Is this section still accurate? I can't find any usage of the property in the code.

Real-Time Pinot table: In case of real-time tables, make sure the "_pinot.server.instance.reload.consumingSegment_" config is set to true inside Server config. Without this, the current consuming segment(s) will not reflect the default null value for newly added columns.

You are right, seems like the default value was switched to true in this PR. https://github.com/apache/incubator-pinot/pull/7078

I mean I grepped through the history and I couldn't find a reference actually reading the config value. I don't think it was ever actually wired. It was weird because we haven't set it and adding fields worked.

Are you saying it works with 0.7.1. release?

yes

@User The next consuming segment will always get the updated schema. The feature is about whether the current consuming segment can add the new columns on the fly via reload

I see, I've found that the usage is through a different constant