[HBASE-21475] Put mutation (having TTL set) added via co-processor is retrieved even after TTL expires

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.0.0, 2.1.1
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 1.4.10, 2.1.3, 2.0.5, 1.3.4
• Component/s: Coprocessors
• Hadoop Flags: Reviewed
• Assignee: Nihal Jain
• Reporter: Nihal Jain
• Created: 13/Nov/18 17:54
• Updated: 07/Oct/19 18:29
• Resolved: 24/Jan/19 01:29

Description

Steps to reproduce

1. 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.
2. Create a table and add a row having TTL set to 3000 ms.
3. Wait for > 3000 ms.
4. 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.