xiarixiaoyao commented on pull request #4910: URL: https://github.com/apache/hudi/pull/4910#issuecomment-1080099081
> yes, let me addressed in another comments. now focus on the questions: One specific question: For an existing table (0.10.1 or prior), Specifically, hoodie.metadata.enable is a writer side config. Readers (Query Engines) will only get to look at evolved schema when they exist as valid schema files. This is what I understood. Is this correct? 1）First of all, this PR does not affect the normal use of metatable. The current version of metaable is turned on by default. The test case in spark3DDL also proves that this PR and metatable can coexist normally. 2) yes, query engine only get to look at evolved schema when they exist as valid schema files. **It must be noted that once schema evolution is enabled, it cannot be closed**, Otherwise, if the internal schema cannot be found, the engine will directly fall back to the original logic of Hudi, which may lead to data reading failure Eg: current schema: ID: string, name: int. now we use schema evolution to change it to ID: decimal, name: string if we delete internalSchema， query engine will fall back to origin read， Obviously, Hudi can't read such data -- 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
