[
https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531668#comment-13531668
]
Andrew Purtell commented on HBASE-7233:
---------------------------------------
bq. For performance sake, we may want to keep the Cell interface to these low
level methods: getTagsArray(), getNumTags(), getTagsOffset(), getTagsLength(),
and then have methods for parsing them [an iterator]
Agreed. My hack-patch does approximately this.
I need to study up on how Cells would be materialized into KeyValues. In the
AccessController we wrap InternalScanners with a filter that looks at each
KeyValue on the way out to the client and evaluates their visibility to the
user. Somehow from the KeyValue API we'd need to get to the cell tags iterator
to extract the ACL (or visibility tag).
A type byte or even making tags name-value pairs would avoid accumulation of
ad-hoc means for distinguishing between them.
Tags stored on disk shouldn't necessarily be sent to clients, though for the
sake of performance we can concede this, where/if streaming on disk encoding
directly to the client.
> Serializing KeyValues
> ---------------------
>
> Key: HBASE-7233
> URL: https://issues.apache.org/jira/browse/HBASE-7233
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.96.0
>
> Attachments: 7233sketch.txt, 7233.txt, 7233-v2.txt,
> 7233v3_encoders.txt, 7233v4_encoders.txt, 7233v5_encoders.txt,
> 7233v6_encoder.txt
>
>
> Undo KeyValue being a Writable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
