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-13448) New Cell implementation with cached component offsets/lengths
Date Fri, 29 May 2015 11:17:17 GMT

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

Anoop Sam John commented on HBASE-13448:

Also one more point to say.  In 0.98 the decision of switching region happens based on KeyValue#heapSizeWithoutTags()
and server also similar decides max #cells to return.  We had bugs around this and fixed..
 Now if we add a KV extension with more heap size and add that extra #bytes in heapSizeWithoutTags()
, similar bug will come again.  Any way in ur test it wont come as all Cells are filtered
at server.  Just saying.  Trunk fixed this issue already and this is only a 2.0 issue.

> New Cell implementation with cached component offsets/lengths
> -------------------------------------------------------------
>                 Key: HBASE-13448
>                 URL: https://issues.apache.org/jira/browse/HBASE-13448
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Scanners
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>         Attachments: 13448-0.98.txt, HBASE-13448.patch, HBASE-13448_V2.patch, HBASE-13448_V3.patch,
gc.png, hits.png
> This can be extension to KeyValue and can be instantiated and used in read path.

This message was sent by Atlassian JIRA

View raw message