You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/27 04:04:00 UTC

[jira] [Updated] (HUDI-578) Trim recordKeyFields and partitionPathFields in ComplexKeyGenerator

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

ASF GitHub Bot updated HUDI-578:
--------------------------------
    Labels: pull-request-available  (was: )

> Trim recordKeyFields and partitionPathFields in ComplexKeyGenerator
> -------------------------------------------------------------------
>
>                 Key: HUDI-578
>                 URL: https://issues.apache.org/jira/browse/HUDI-578
>             Project: Apache Hudi (incubating)
>          Issue Type: Improvement
>            Reporter: leesf
>            Assignee: leesf
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.2
>
>
> when use ComplexKeyGenerator
> the options the below.
> {code:java}
> option("hoodie.datasource.write.recordkey.field", "name, age").
> option("hoodie.datasource.write.keygenerator.class", ComplexKeyGenerator.class.getName()).
> option("hoodie.datasource.write.partitionpath.field", "location, age").
> {code}
> and the data is 
> {code:java}
> "{ \"name\": \"name1\", \"ts\": 1574297893839, \"age\": 15, \"location\": \"latitude\", \"sex\":\"male\"}"
> {code}
> the result is incorrect with age = null in recordkey, and age = default in partitionpath.
> We would trim the paritions and recordkeys in complexKeyGenerator



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