[ https://issues.apache.org/jira/browse/HBASE-8496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708649#comment-13708649 ]
Andrew Purtell commented on HBASE-8496: --------------------------------------- bq. So HFileV3 would be the one which would know about the Tags and the read and write path in HFileV3 would understand tags. What I especially like about this is any performance or functional risks which might possibly be introduced by the tags work is completely optional to take on this way - just don't select HFileV3. We can even mark it as experimental until 0.98. I have been able to observe Ram's work over the past couple of months trying out various other approaches just shy of introducing a new file format. It's not a decision come to overnight. +1 > 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