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 2022/10/04 14:52:00 UTC
[jira] [Assigned] (HUDI-3411) Incorrect Record Key Field property Handling
[ https://issues.apache.org/jira/browse/HUDI-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sivabalan narayanan reassigned HUDI-3411:
-----------------------------------------
Assignee: Jonathan Vexler (was: Raymond Xu)
> Incorrect Record Key Field property Handling
> --------------------------------------------
>
> Key: HUDI-3411
> URL: https://issues.apache.org/jira/browse/HUDI-3411
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Alexey Kudinkin
> Assignee: Jonathan Vexler
> Priority: Blocker
> Fix For: 0.13.0
>
>
> Currently `HoodieTableConfig#getRecordKeyFieldProp` returns a single String, even though it could contain a *list* of columns making up composite Primary Key.
> {code:java}
> public String getRecordKeyFieldProp() {
> return getStringOrDefault(RECORDKEY_FIELDS, HoodieRecord.RECORD_KEY_METADATA_FIELD);
> } {code}
>
> Most of the callers of this method are actually not handling this correctly, assuming that the Record Key is always a single field.
> NOTE: While concatenation of CPK seems like a very natural step here, special care has to be taken, since Composite PK can NOT be concatenated as strings, as this might break the uniqueness constraint.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)