[
https://issues.apache.org/jira/browse/HBASE-13579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-13579:
-------------------------------------------
Affects Version/s: (was: 2.0.0)
1.0.0
1.0.1
Fix Version/s: 1.0.0
1.0.1
0.98.13
1.1.0
2.0.0
Pushed to branch-1 +
> Avoid isCellTTLExpired() for NO-TAG cases
> -----------------------------------------
>
> Key: HBASE-13579
> URL: https://issues.apache.org/jira/browse/HBASE-13579
> Project: HBase
> Issue Type: Sub-task
> Components: Scanners
> Affects Versions: 1.0.0, 1.0.1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 1.0.0, 2.0.0, 1.0.1, 1.1.0, 0.98.13
>
> Attachments: HBASE-13579_0.98.patch, HBASE-13579_1.patch,
> HBASE-13579_2.patch, HBASE-13579_KVExtension.patch,
> HBASE-13579_branch-1.patch, HBASE-13579_branch-1_1.patch,
> HBASE-13579_storelevel.patch
>
>
> As observed in this JIRA's performance test, we are always calling the
> isCellTTLExpired() for every cell and internally it is parsing the keyLength,
> valueLength() to get the tagsLength after which we decide whether Cell level
> TTL is present are not.
> This JIRA aims to avoid this check if all the readers of the storescanner
> knows that there are no tags to read. Note that, for the memstore scanner we
> will do that in another JIRA, which I suppose Stack had already raised to
> avoid tag length while flushing (for the NO-TAG) case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
