walterddr opened a new issue #8046: URL: https://github.com/apache/pinot/issues/8046
Currently table config validation are not just triggered when table config is being add/updated. some part of the validation code is also used outside of table config change code path. several issues we want to fix. 1. ensure that table config validation only runs when table config are being updated/added because it is the only codepath that supports a user manual SKIP option. (see #7921) 2. other types of validation (such as schema validation) should not be triggered when table config is being validate since table config doesn't contain schema. Additionally, for backward compatibility, we should not run validation against existing, stored configs because it blocks seamless upgrade from older pinot version to newer one. -- 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 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
