You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Jonathan Vexler (Jira)" <ji...@apache.org> on 2024/09/24 19:28:00 UTC

[jira] [Closed] (HUDI-8187) Hudi 1.0 reader should be able to read both 1.0 and 0.x tables with custom key generator

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

Jonathan Vexler closed HUDI-8187.
---------------------------------
    Resolution: Fixed

> Hudi 1.0 reader should be able to read both 1.0 and 0.x tables with custom key generator
> ----------------------------------------------------------------------------------------
>
>                 Key: HUDI-8187
>                 URL: https://issues.apache.org/jira/browse/HUDI-8187
>             Project: Apache Hudi
>          Issue Type: Improvement
>            Reporter: Ethan Guo (this is the old account; please use "yihua")
>            Assignee: Lokesh Jain
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> We changed the format of partition field table config "{{{}hoodie.table.partition.fields{}}}" for custom keygen on master and Hudi 1.0.  Hudi 1.0 reader should be able to read both 1.0 and 0.x tables with custom key generator and different partition field table config formats.
>  
> For 0.x tables, we should consider both old format, i.e., 0.15.0 behavior where partition field type and timestamp configs maybe unknown for custom keygen, and the case where partition field type and timestamp configs are added.
> The PR also handles the logic where partition path field config `hoodie.datasource.write.partitionpath.field` is derived from existing table config so that it uses the custom keygen partition type when available.



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