hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8496) Implement tags and the internals of how a tag should look like
Date Wed, 05 Jun 2013 22:48:20 GMT

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

stack commented on HBASE-8496:

A few notes on above Ram.

bq. <1 byte type code><2 byte tag length><tag>

You don't want to use a vint for length?  Most tags will only need a single byte for length
I'd imagine.

Have we said what tags will actually look like?  For instance for ACL and Visibility, what
will they look like?  Will a tag for Visibility be the Accumulo list of who can view?

On the 1 byte type, I am not clear why.

Would suggest too that you start up a one or two page design doc.  Will help w/ review of
design.  Easier than trying to aggregate JIRA comments spread over multiple issues.

Do you think we need tag iterators?  Is that overkill since for the vast majority of cases
there will be one tag or two at most? (I'd guess).

Tags will be done by a CP?  Does it have to be that way?  Can tags not be first class beside
timestamp, column qualifier, etc.

bq. If we are having the structure with the type in it then it may not be possible to actually
have some validation on the client side for specific tag types.

Pardon me, I do not follow the above.

Is putting tags after value a good idea?  We'll have to skip over the value to see if we should
return the KV?  Would be easier if the tag were part of the key?

Sounds like we need to change the hfileformats (smile)?

"option tag part" is optionally adding tags to hfile?

Good on you Ram.
> 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

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

View raw message