[
https://issues.apache.org/jira/browse/HBASE-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234966#comment-14234966
]
Anoop Sam John commented on HBASE-11639:
----------------------------------------
bq.While we are on the subject, the thing I did not fully understand in this
patch and also in HBASE-11920 was that why do we do this way of getting a RE
from config, then replacing that with a one coming from a CP.
This Jira or HBASE-11920 is NOT adding any new config for reading RE class
name. It adds a new CP which can wrap the system's RE. (plugged in or default)
bq.The RE is already pluggable, shouldn't the user configure RE accordingly,
and then configure what RE to wrap in this new RE implementation rather.
You mean VC introducing new RE and asking users to configure that. Also the
VC's RE impl to introduce again one more config to read the actual RE to be
used. VC's RE is just a wrapper. I feel this is difficult in user perspective.
Too many configs. For AC/VC what we ask user is to just configure the CPs. If
those can do this simple wrap in some way, that is better no? Am I missing
some thing?
[~apurtell] Do you still have concern over usage of custom RE?
> [Visibility controller] Replicate the visibility of Cells as strings
> --------------------------------------------------------------------
>
> Key: HBASE-11639
> URL: https://issues.apache.org/jira/browse/HBASE-11639
> Project: HBase
> Issue Type: Improvement
> Components: Replication, security
> Affects Versions: 0.98.4
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Labels: VisibilityLabels
> Fix For: 1.0.0, 2.0.0
>
> Attachments: HBASE-11639_amend.patch, HBASE-11639_v11.patch,
> HBASE-11639_v13.patch, HBASE-11639_v13.patch, HBASE-11639_v14.patch,
> HBASE-11639_v15.patch, HBASE-11639_v16.patch, HBASE-11639_v17.patch,
> HBASE-11639_v2.patch, HBASE-11639_v2.patch, HBASE-11639_v3.patch,
> HBASE-11639_v3.patch, HBASE-11639_v5.patch, HBASE-11639_v6.patch,
> HBASE-11639_v9.patch
>
>
> This issue is aimed at persisting the visibility labels as strings in the WAL
> rather than Label ordinals. This would help in replicating the label
> ordinals to the replication cluster as strings directly and also that after
> HBASE-11553 would help because the replication cluster could have an
> implementation as string based visibility labels.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
