[
https://issues.apache.org/jira/browse/HBASE-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234485#comment-14234485
]
Andrew Purtell edited comment on HBASE-11639 at 12/4/14 7:06 PM:
-----------------------------------------------------------------
One higher level question I have about this whole design is what happens if we
want to replicate visibility tags as Strings over an existing custom
ReplicationEndpoint? That won't be guaranteed today because an endpoint is
implemented by a single class, there's no opportunity for mixing in
functionality, each implementation must take care to delegate. Sorry I couldn't
come here earlier, and anyway what has been committed is fine, the
VisibilityReplicationEndpoint delegates to whatever it finds in place, but we
should figure out what is the best next step here, if any. One option would be
introducing a replication observer interface - ReplicationObserver - and
coprocessor upcall chains out of replication code. Custom replication endpoint
specification could be extended to allow specification of observer stacks.
/cc [~lhofhansl] [~jesse_yates]
was (Author: apurtell):
One higher level question I have about this whole design is what happens if we
want to replicate visibility tags as Strings over an existing custom
ReplicationEndpoint? That won't be possible today because an endpoint is
implemented by a single class, there's no opportunity for mixing in
functionality. Sorry I couldn't come here earlier, and anyway what has been
committed is fine, but we should figure out what is the best next step here, if
any. One option would be introducing a replication observer interface -
ReplicationObserver - and coprocessor upcall chains out of replication code.
Custom replication endpoint specification could be extended to allow
specification of observer stacks.
/cc [~lhofhansl] [~jesse_yates]
> [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)
