[
https://issues.apache.org/jira/browse/HBASE-21475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain updated HBASE-21475:
-------------------------------
Description:
*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 retrieved even after TTL expires.
was:
*Steps to reproduce*
1) Create a region coprocessor an override {{preBatchMutate}} such that it
create a put corresponding to a user put having same timestamp and TTL as the
user put.
2) Create a table and add a row having TTL set to 3000 ms
3) Wait for > 3000 ms
4) Scan the table.
*Result*
User row is not retreived while put created via coprocessor is still retreived.
*Analysis/Issue*
Unlike user mutations, the mutations added by coprocessor do not have tags
corresponding to TTL, hence they retreived even after TTL expires.
> 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
>
> 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 retrieved even after TTL expires.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
