[
https://issues.apache.org/jira/browse/HBASE-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695002#comment-13695002
]
Andrew Purtell commented on HBASE-8496:
---------------------------------------
My read is tags are in core but the example users are coprocessors. Except for
the operation attribute part, but that's just the other side of the story: if a
cp is consuming tags presumably it is setting/managing them too.
To what extent are we comfortable changing the client API to be tags aware? In
0.94 too?
bq. Could hfile blocks be cellblocks? And in meta data for hfile say what
decoder to use?
I think it makes sense to have one codec for cells, or transitionally cells as
two distinct serializers - keyvalue+tags, leaving the keyvalue class alone for
the most part. We have keyvaluecodec in both trunk/0.95 and 0.94. Right now its
only used for WALs. Should extend this to use for HFile blocks too - one common
codec for keyvalue/cell serialization dealing with stuff like tags. So agreed
hfile block encoding should change at least to incorporate this new common
interface. If we have leeway to change how HFile blocks are constructed, maybe
we can bump HFile minor and try more than just cell by cell. Could pack tags
together at the block level (and even dedup/share) if we can go this far with
the kind of changes people would be comfortable with in trunk *and* 0.94.
> Implement tags and the internals of how a tag should look like
> --------------------------------------------------------------
>
> Key: HBASE-8496
> URL: https://issues.apache.org/jira/browse/HBASE-8496
> Project: HBase
> Issue Type: New Feature
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.98.0
>
> Attachments: Tag design.pdf
>
>
> The intent of this JIRA comes from HBASE-7897.
> This would help us to decide on the structure and format of how the tags
> should look like.
--
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
