gortiz opened a new issue, #10550: URL: https://github.com/apache/pinot/issues/10550
Each Pinot index have their own constraints. For example, a column of type integer should not have a TEXT index and one with raw encoding should not have a FST index. These constraints are enforced in different ways around the code, which violates RAW and makes it more difficult to change these constraints (as the developer needs to know all the places where the constraint is enforced). There are also some situations where even when the customer explicitly ask to disable some index or use some specific encoding, the presence of some specific index implies that what the customer explicitly ask is ignored. There have been some efforts to centralize how these constraints are enforced. For example, `TableConfigUtils.validateIndexConfigs`. But now that we can add indexes, that utility method cannot cover all cases. Ideally we should extend IndexType in order to support some kind of validation -- 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
