9aman opened a new pull request, #12043: URL: https://github.com/apache/pinot/pull/12043
A column should be of Dictionary type for it to have inverted index. Current Scenario: A config will be flagged as **invalid** during upsert of table config if the a column is marked as **noDictionaryColumn** and has inverted index enabled. e.g. [invalid_table_config.json](https://github.com/apache/pinot/files/13442766/invalid_table_config.json) Issues: Field Config List can also be used to mark the column's encoding type as RAW (or no dictionary) and enable inverted index on it. Resoltion: This PR aims to put similar checks for columns in Field Config List as well e.g. [invalidConfig_field_config_list.json](https://github.com/apache/pinot/files/13442802/invalidConfig_field_config_list.json) The response of current and new code on an table config upsert ( [invalidConfig_field_config_list.json](https://github.com/apache/pinot/files/13442845/invalidConfig_field_config_list.json) ) will be following: Current code: config gets inserted [prev_resultant_config.json](https://github.com/apache/pinot/files/13442849/prev_resultant_config.json) New Code: Throws an error: {"code":400,"error":"Invalid TableConfigs. Invalid TableConfigs: transcript2. Cannot create an Inverted Index on column: lastName, specified as a non dictionary column"} -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
