hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13393) Add facility to disable tags after parent goes in
Date Sat, 23 May 2015 07:47:17 GMT

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

ramkrishna.s.vasudevan commented on HBASE-13393:

bq.Also the boolean can we just make it non volatile only?
bq.We are still doing volatile boolean read on each update to memstore
Okie.  We can change to non-volatile.
bq.In 90+% of cases, tags are not used? What if a table or column family config to say 'use
There is no such feature we have.  Tags are not supported directly from clients.  Tags are
now added to Cells only in the server side as part of ACL or Visibilities. The client passes
these information only as Attributes. 
The reverse where a server sends a Tag to the client is also not there except in the case
of replication or cell replay where we use WalCodec (in case of WAL replay).

> 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

View raw message