[
https://issues.apache.org/jira/browse/HBASE-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651587#comment-13651587
]
Matt Corgan commented on HBASE-8496:
------------------------------------
As for existing encoders, I think someone will have to go back and add tag
encoding support to them, else they'll be a black hole for tags. Tags will go
in, but none will come out.
I don't have any use cases in mind for tags, but to share what i was
envisioning: the tags section could be composed of a sorted list of byte[]s of
the form: [vint numTags][vint length0][byte[] tag0][vint lengthN][byte[] tagN].
Should probably sort them at write time so it only has to happen once. Assume
there will be >=1 reads so might as well sort when writing.
If the basic structure above is followed, then encoders can use dictionary or
trie style encoding for the tag section.
> 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
>
>
> 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
