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

Hudson commented on HBASE-21475:
--------------------------------

Results for branch branch-1.3
        [build #624 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/624/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/624//General_Nightly_Build_Report/]


(/) {color:green}+1 jdk7 checks{color}
-- For more information [see jdk7 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/624//JDK7_Nightly_Build_Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/624//JDK8_Nightly_Build_Report_(Hadoop2)/]




(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Put mutation (having TTL set) added via co-processor is retrieved even after 
> TTL expires
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-21475
>                 URL: https://issues.apache.org/jira/browse/HBASE-21475
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors
>    Affects Versions: 3.0.0, 2.0.0, 2.1.1
>            Reporter: Nihal Jain
>            Assignee: Nihal Jain
>            Priority: Major
>             Fix For: 3.0.0, 1.5.0, 2.2.0, 1.4.10, 2.1.3, 2.0.5, 1.3.4
>
>         Attachments: HBASE-21475.master.001.patch
>
>
> *Steps to reproduce*
>  # Create a region co-processor and override {{preBatchMutate}} such that it 
> creates a put corresponding to a user put having same timestamp and TTL as 
> the user put.
>  # Create a table and add a row having TTL set to 3000 ms.
>  # Wait for > 3000 ms.
>  # Scan the table.
> *Expected Result*
>  No rows should be retrieved in step 4
> *Actual Result*
>  User row is not retreived, while put created via co-processor is still 
> retrieved.
> *Analysis/Issue*
>  Unlike user mutations, the mutations added by coprocessor do not have tags 
> corresponding to TTL, hence they are retrieved in scan even after TTL expires.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to