sajjad-moradi opened a new issue, #10868: URL: https://github.com/apache/pinot/issues/10868
If a column is added to the schema and there's also an index defined for that column, the older segments which were built by older schema/table config cannot be purged with the following exception: ``` Cannot create index for column: XYZ because it is not in schema. ``` This is because SegmentColumnarIndexCreator assumes that schema and table config are always in-sync. That's a valid assumption - other than the old segment scenario mentioned above - because validation put in place in table config rest endpoint makes sure that if an index is added to the table config, that column should be present in the schema. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
