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

Lokesh Jain updated HUDI-6660:
------------------------------
    Description: Currently merge into fails when primary key is a complex key 
and join conditions do not include all the primary key columns. The Jira aims 
to restrict the constraint only when optimized writes are enabled. With the 
optimized writes disabled, merge into doesn't update the records if the primary 
key does not match completely.  (was: Currently merge into fails when primary 
key is a complex key and join conditions do not include all the primary key 
columns. The Jira aims to relax this requirement to allow join even on a subset 
of primary key columns.)

> For merge into use primary key constraint when optimized writes are enabled
> ---------------------------------------------------------------------------
>
>                 Key: HUDI-6660
>                 URL: https://issues.apache.org/jira/browse/HUDI-6660
>             Project: Apache Hudi
>          Issue Type: Bug
>          Components: spark-sql
>            Reporter: Lokesh Jain
>            Priority: Major
>              Labels: pull-request-available
>
> Currently merge into fails when primary key is a complex key and join 
> conditions do not include all the primary key columns. The Jira aims to 
> restrict the constraint only when optimized writes are enabled. With the 
> optimized writes disabled, merge into doesn't update the records if the 
> primary key does not match completely.



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

Reply via email to