[
https://issues.apache.org/jira/browse/HUDI-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Guo updated HUDI-5875:
----------------------------
Fix Version/s: (was: 0.15.0)
> Fix index look/matching records for MERGE INTO with MOR table
> -------------------------------------------------------------
>
> Key: HUDI-5875
> URL: https://issues.apache.org/jira/browse/HUDI-5875
> Project: Apache Hudi
> Issue Type: Improvement
> Components: spark-sql, writer-core
> Reporter: sivabalan narayanan
> Priority: Critical
> Fix For: 0.16.0
>
>
> MERGE INTO statement w/ MOR table might result go wrong in some corner case.
>
> where a record is valid as per base file, but has gotten a delete in log
> files,
> following this, if a user executes below MERGE_INTO statement
> {code:java}
> merge into hudi_table2 using (select * from source) as b on (hudi_table2.id =
> b.id and hudi_table2.name=b.name) when not matched then insert *; {code}
> In this case, a record that was deleted in log file, might appear as though
> its valid record w/ our index look up.
>
> This will not be an issue w/ COW table or after compaction kicks in.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
