hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13579) Avoid isCellTTLExpired() for NO-TAG cases
Date Tue, 28 Apr 2015 13:02:06 GMT

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

Anoop Sam John commented on HBASE-13579:
----------------------------------------

Also we have another Jira to cache some of the lengths in the Cell impl.  I think that is
a must as we refine the CellComparator further. May be the getTagsLength solution go in there
directly?  TagsLength also we will cache? cc [~stack]

> 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: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-13579_KVExtension.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)

Mime
View raw message