[
https://issues.apache.org/jira/browse/PHOENIX-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-4070:
----------------------------------
Labels: secondary_index (was: )
> Delete row should mask upserts at same timestamp
> ------------------------------------------------
>
> Key: PHOENIX-4070
> URL: https://issues.apache.org/jira/browse/PHOENIX-4070
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Labels: secondary_index
> Fix For: 4.12.0, 4.11.1
>
> Attachments: PHOENIX-4070_v1.patch
>
>
> If a delete row (i.e. DeleteFamily) occurs at the same timestamp as an upsert
> (i.e. Put), then the delete must mask the puts, regardless of when the
> mutations actually hit the server. Currently, this is a problem if the delete
> is processed first and the upsert ends up writing a row to the index table
> when it shouldn't.
> Unlike PHOENIX-4058, we cannot work around the issue by setting STORE_NULLS
> to true.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
