Yes ,you are right. if the HA_ERR_FOUND_DUPP_KEY is caused by a duplicate unique key with a different primary key , the fix for UPDATE_ROWS_EVENT would failed.
the HA_ERR_KEY_NOT_FOUND caused by UPDATE_ROWS_EVENT may also be failed to fix if inserting a record was failed (there is a duplicate unique key)
The two kinds of cases have let me confused for a long time.
Actually the code to handle HA_ERR_FOUND_DUPP_KEY caused by UPDATE_ROWS_EVENT is removed in our production environment because someone think it's too crude to delete a record.
I hope someone of Percona Or other people who are familiar with the source code can help perfect this patch :)
Hi, Raghavendra
Yes ,you are right. if the HA_ERR_ FOUND_DUPP_ KEY is caused by a duplicate unique key with a different primary key , the fix for UPDATE_ROWS_EVENT would failed.
the HA_ERR_ KEY_NOT_ FOUND caused by UPDATE_ROWS_EVENT may also be failed to fix if inserting a record was failed (there is a duplicate unique key)
The two kinds of cases have let me confused for a long time.
Actually the code to handle HA_ERR_ FOUND_DUPP_ KEY caused by UPDATE_ROWS_EVENT is removed in our production environment because someone think it's too crude to delete a record.
I hope someone of Percona Or other people who are familiar with the source code can help perfect this patch :)