hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10861) Supporting API in ByteRange
Date Fri, 25 Apr 2014 00:09:16 GMT

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

Andrew Purtell commented on HBASE-10861:

bq. The deserailzation logic creates a read only copy of the block cache data. I think we
need to have this behaviour to have read only byte ranges also.  What do you say?

Not getting why we just wouldn't scribble on the block cache data.

Anyway sounds like the idea is to have read only ByteRanges by default and a MutableByteRange
when not, and that would be good.

> Supporting API in ByteRange
> ---------------------------
>                 Key: HBASE-10861
>                 URL: https://issues.apache.org/jira/browse/HBASE-10861
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-10861.patch, HBASE-10861_2.patch
> We would need APIs that would 
> setLimit(int limit)
> getLimt()
> asReadOnly()
> These APIs would help in implementations that have Buffers offheap (for now BRs backed
by DBB).
> If anything more is needed could be added when needed.

This message was sent by Atlassian JIRA

View raw message