[GitHub] [hudi] voonhous commented on issue #8018: [SUPPORT] why is the schema evolution done while not setting hoodie.schema.on.read.enable

["voonhous (via GitHub)" <gi...@apache.org>]

voonhous commented on issue #8018:
URL: https://github.com/apache/hudi/issues/8018#issuecomment-1451247400

   @menna224 
   
   Prior to Hudi Full schema evolution (HFSE), which is enabled using `hoodie.schema.on.read.enable=true`, Hudi relies on Avro's Schema resolution (ASR) to perform schema evolution. 
   
   What you are encountering is basically schema-evolution performed via ASR. I've written some test and fixes that are unrelated to your issue before where you can get an idea of how it is different from HFSE here:
   https://github.com/apache/hudi/issues/7444
   
   I noticed that you are using 0.12.*, not sure which minor version you are using, but it doesn't really matter. In the 0.12.* branches, HFSE is an experimental feature and the feature that you wanted that was governed by `hoodie.datasource.write.reconcile.schema` was essentially changed to be adapted for HFSE's use.
   
   As such, you will not be able to use `hoodie.datasource.write.reconcile.schema` to prevent schemas from being implicitly evolved. 
   
   I hope this answers questions that you have.
   
   With regards to how one can prevent schema from being evolved implicitly when ASR is used... I don't think it's possible in 0.12.*. (Anyone in the community that is more familiar with this, please correct me if I am wrong)


-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org