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 2021/08/04 04:54:00 UTC

[jira] [Assigned] (HUDI-2268) Upgrade hoodie table to 0.9.0

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

sivabalan narayanan reassigned HUDI-2268:
-----------------------------------------

    Assignee: sivabalan narayanan

> Upgrade hoodie table to 0.9.0
> -----------------------------
>
>                 Key: HUDI-2268
>                 URL: https://issues.apache.org/jira/browse/HUDI-2268
>             Project: Apache Hudi
>          Issue Type: Sub-task
>          Components: Usability
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Major
>             Fix For: 0.9.0
>
>
> Wrt upgrading/downgrading hoodie.properties, here is what we can go. 
> Add a new table version, 2. 
> Add an upgrade step:
> before every write operation. 
>      Check if existing hoodie.props is in an older version. If yes, perform upgrade step to version2 (either from 0 to 2 or from 1 to 2). This essentially means that we need to add new properties pertaining to sql dml to hoodie.properties. 
> Things to watch out for:
> for some operations, not all props might be set by the user. So, we might need to throw an exception. (record key field, partition path field, key gen prop, precombine field). 
> We need to fetch latest table schema since the incoming df could have partial cols.
>  
> Downgrade step: 
> hoodie.properties will have some additional properties. Should not cause any harm. All we need to do is to downgrade the table version to target version and not touch any of the props. 
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)