You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/11/05 02:40:27 UTC

[jira] [Updated] (PHOENIX-2375) Bypass write of Tephra delete markers before preBatchMutate called

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

James Taylor updated PHOENIX-2375:
----------------------------------
    Attachment: PHOENIX-2375.patch

[~tdsilva] - please review. The only test failure is caused by a bug that is fixed in master. The extra call to generateDeletes() was masking this. We can confirm when the merge is complete.

> Bypass write of Tephra delete markers before preBatchMutate called
> ------------------------------------------------------------------
>
>                 Key: PHOENIX-2375
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2375
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: James Taylor
>         Attachments: PHOENIX-2375.patch
>
>
> Send Tephra family delete markers instead of real delete family markers to bypass the Tephra coprocessor preDelete hook that writes the Tephra family delete marker immediately. This ensures that the preBatchMutate hook sees the previous state correctly and prevents a second unnecessary call to the Phoenix preBatchMutate hook.
> In addition, removing unnecessary call to generateDeletes for new data table rows.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)