You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2023/02/05 05:15:00 UTC

[jira] [Assigned] (HUDI-5704) Col drop config is not honored when schema validation is disabled

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

sivabalan narayanan reassigned HUDI-5704:
-----------------------------------------

    Assignee: sivabalan narayanan

> Col drop config is not honored when schema validation is disabled
> -----------------------------------------------------------------
>
>                 Key: HUDI-5704
>                 URL: https://issues.apache.org/jira/browse/HUDI-5704
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: writer-core
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Major
>
> [https://dev.azure.com/apache-hudi-ci-org/785b6ef4-2f42-4a89-8f0e-5f0d7039a0cc/_apis/build/builds/14920/logs/38]
>  
> looks like col drop flag is tightly coupled w/ schema validation flag. only if schema validation is enabled, col drop flag is honored. if not, it may succeed. 
>  
> for eg, 
> if table schema is col1, col2, col3
> and new incoming schema is col1, col2
> col drop config is set to false (which means col drop should not be supported), and schema validation is set to false, commit will succeed. Expectation is, commit should fail for this new batch. 
>  
>  
>  



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