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

Hudson commented on HBASE-19384:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4174 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4174/])
HBASE-19384 Results returned by preAppend hook in a coprocessor are (stack: rev 
1856237e2dae6505558bb72ee063839c48ab0e9e)
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/ObserverContext.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionObserver.java
* (edit) 
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionObserverBypass.java


> Results returned by preAppend hook in a coprocessor are replaced with null 
> from other coprocessor even on bypass
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19384
>                 URL: https://issues.apache.org/jira/browse/HBASE-19384
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19384.master.001.patch
>
>
> Phoenix adding multiple coprocessors for a table and one of them has 
> preAppend and preIncrement implementation and bypass the operations by 
> returning the results. But the other coprocessors which doesn't have any 
> implementation returning null and the results returned by previous 
> coprocessor are override by null and always going with default implementation 
> of append and increment operations. But it's not the case with old versions 
> and works fine on bypass.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to