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

Mehdi Salarkia updated PHOENIX-6187:
------------------------------------
    Description: 
When there is an UPSERT with an ON DUPLICATE KEY condition, if the region 
mutation response is a failure it gets ignore and silently swallowed resulting 
in silent write failures. 

This is a major issue resulting in client assuming the write was successful 
while it actually was not. 

Also see another report 
[https://lists.apache.org/thread.html/ra229cea951236d9c48d06ec137f415997f0acb0d99078a6c19290c0e%40%3Cdev.phoenix.apache.org%3E]

 Which could be cause by this issue.

  was:
When there is an UPSERT with an ON DUPLICATE KEY condition, if the region 
mutation response is a failure it gets ignore and silently swallowed resulting 
in silent write failures. 

This is a major issue resulting in client assuming the write was successful 
while it actually was not. 

Also see another report 
[https://lists.apache.org/thread.html/ra229cea951236d9c48d06ec137f415997f0acb0d99078a6c19290c0e%40%3Cdev.phoenix.apache.org%3E]

 


>  Avoid swallowing UPSERT... ON DUPLICATION KEY UPDATE failures
> --------------------------------------------------------------
>
>                 Key: PHOENIX-6187
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6187
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Mehdi Salarkia
>            Assignee: Mehdi Salarkia
>            Priority: Critical
>
> When there is an UPSERT with an ON DUPLICATE KEY condition, if the region 
> mutation response is a failure it gets ignore and silently swallowed 
> resulting in silent write failures. 
> This is a major issue resulting in client assuming the write was successful 
> while it actually was not. 
> Also see another report 
> [https://lists.apache.org/thread.html/ra229cea951236d9c48d06ec137f415997f0acb0d99078a6c19290c0e%40%3Cdev.phoenix.apache.org%3E]
>  Which could be cause by this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to