You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Zhaojing Yu (Jira)" <ji...@apache.org> on 2022/10/01 12:18:00 UTC

[jira] [Updated] (HUDI-4010) DynamoDB lock configs for naming/docs could be improved

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

Zhaojing Yu updated HUDI-4010:
------------------------------
    Status: Patch Available  (was: In Progress)

> DynamoDB lock configs for naming/docs could be improved
> -------------------------------------------------------
>
>                 Key: HUDI-4010
>                 URL: https://issues.apache.org/jira/browse/HUDI-4010
>             Project: Apache Hudi
>          Issue Type: Improvement
>            Reporter: Udit Mehrotra
>            Assignee: Ethan Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.12.1
>
>
> The issue was raised in [https://github.com/apache/hudi/issues/5451,] where the customer created the DynamoDB table manually and assumed *partition_key* property to be the column name that is to be used instead of the actual value of the partition key column. The name of the partition key column is fixed in code to {*}key{*}.
>  
> There is scope to improve the naming, so it is not confusing whether one needs to define a columns name there or the column value to be used for that specific table. Also may be we can better document that the table can be created automatically by Hudi code, and if at all someone creates table by themselves, what column name to use.



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