[
https://issues.apache.org/jira/browse/HBASE-21475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16750657#comment-16750657
]
Hudson commented on HBASE-21475:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #521 (See
[https://builds.apache.org/job/HBase-1.3-IT/521/])
HBASE-21475 Put mutation (having TTL set) added via co-processor is (apurtell:
[https://github.com/apache/hbase/commit/d4d7efb80c082b12e901c811ef7ff11676eef460])
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionObserverForAddingMutationsFromCoprocessors.java
> 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)
