phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3892) Allow regionobserver to optionally skip postPut/postDelete when postBatchMutate was called
Date Fri, 26 May 2017 21:33:04 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026880#comment-16026880
] 

Lars Hofhansl commented on PHOENIX-3892:
----------------------------------------

Arrghh... Accidentally files as a PHOENIX issue. If I can't move it, I'll just close.

> Allow regionobserver to optionally skip postPut/postDelete when postBatchMutate was called
> ------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3892
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3892
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>
> Right now a RegionObserver can only statically implement one or the other. In scenarios
where we need to work sometimes on the single postPut and postDelete hooks and sometimes on
the batchMutate hooks, there is currently no place to convey this information to the single
hooks. I.e. the work has been done in the batch, skip the single hooks.
> There are various solutions:
> 1. Allow some state to be passed _per operation_.
> 2. Remove the single hooks and always only call batch hooks (with a default wrapper for
the single hooks).
> 3. more?
> [~apurtell], what we had discussed a few days back.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message