You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Alexey Kudinkin (Jira)" <ji...@apache.org> on 2022/12/13 21:55:00 UTC

[jira] [Closed] (HUDI-5296) Support disabling schema on read if not required

     [ https://issues.apache.org/jira/browse/HUDI-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kudinkin closed HUDI-5296.
---------------------------------
    Resolution: Fixed

> Support disabling schema on read if not required
> ------------------------------------------------
>
>                 Key: HUDI-5296
>                 URL: https://issues.apache.org/jira/browse/HUDI-5296
>             Project: Apache Hudi
>          Issue Type: Improvement
>          Components: writer-core
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.12.2
>
>
> If someone has enabled "schema.on.read" by mistake for a given table, as of now, they can't disable it back. we are seeing some corner case bugs that schema on read has bugs around insert_overwrite, reconcile schema etc. So, atleast for those who hasn't done any renaming or dropping a column, it should be feasible to disable schema on read on the write path and make progress. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)