[
https://issues.apache.org/jira/browse/HBASE-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559235#comment-14559235
]
stack commented on HBASE-13393:
-------------------------------
So, the check of tags length is cheap because it is a hardcoded '0. 99% of the
time (except for ACL, etc.), there will be no tags so we'll not be writing the
volatile boolean (nor reading the volatile boolean if do what Sean says above).
That sounds good to me.
> Add facility to disable tags after parent goes in
> -------------------------------------------------
>
> Key: HBASE-13393
> URL: https://issues.apache.org/jira/browse/HBASE-13393
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Attachments: HBASE-13393.patch, HBASE-13393_1.patch
>
>
> We used to specify 'no tags' by choosing to write files that were version 2.
> After parent goes in, make it so can ask a v3 file not to write tags.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
