codope commented on pull request #3830: URL: https://github.com/apache/hudi/pull/3830#issuecomment-951772398
> trying to understand why do we need this change? metadata table is something internally managed. I prefer to enable schema validation always. I would prefer to validate the schema as well. This change is just to avoid the flakiness in [TestHoodieDeltaStreamer.testAsyncClusteringServiceWithCompaction](https://dev.azure.com/apache-hudi-ci-org/785b6ef4-2f42-4a89-8f0e-5f0d7039a0cc/_apis/build/builds/2725/logs/61). By default the schema validation is turned off. It was hardcoded to true for metadata table. However, on a high level, my thinking is even though the metadata table is internally managed shouldn't we have the data table configs govern the metadata table configs as well instead of hardcoding values? This may not be true for all configs but for some we can inherit the configs directly from the data table. For instance, let's take the scehma validation config. For whatever reason (efficiency, or avoid validation failure), user wants it to be turned off doesn't it make sense to turn it off for the metadata table as well for those same reasons? -- 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...@hudi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
