[
https://issues.apache.org/jira/browse/HBASE-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394590#comment-14394590
]
Sean Busbey commented on HBASE-13393:
-------------------------------------
If you don't use tags, then the hfiles after compaction effectively already
look like you'd have if you requested no tag support. Is the extra config worth
the savings on optimizing the flush?
Could we instead track if there are any tags in a store and then do the same
optimization on flush as we do in compaction?
> 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
>
> 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)
