This message was deleted.
# general
s
This message was deleted.
a
what do you mean by "as it now can be queried as well"? Brokers don't query unused segments when building table schema
r
I meant how it will handle with segments queried from https://druid.apache.org/docs/latest/querying/query-deep-storage/
as those could also have a different schema
a
I see what you mean now.
r
maybe this feature just still load the segment info in the ZK/historicals, but do not load the data on the historicals, so it already handle leastRestrictive perfectly
a
that drift/difference between off-historical/unused segments and used segments can indeed become an issue. Right now, the assumption is that the schema is the same. Though in future druid releases, some of us are thinking of devising a different mechanism for building table schema. A mechanism that doesn't rely on a segment being used.
once that materializes, a column that is only in the unused segment, can be queried from deep storage