You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/01/08 20:20:35 UTC
[jira] [Commented] (HBASE-12823) Visibility label security at
limited localized level
[ https://issues.apache.org/jira/browse/HBASE-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269888#comment-14269888 ]
Sean Busbey commented on HBASE-12823:
-------------------------------------
do we have some measurements of the performance impact on tables that aren't using visibility labels?
> Visibility label security at limited localized level
> ----------------------------------------------------
>
> Key: HBASE-12823
> URL: https://issues.apache.org/jira/browse/HBASE-12823
> Project: HBase
> Issue Type: Improvement
> Components: security
> Affects Versions: 1.0.0, 2.0.0, 0.98.10
> Reporter: Jerry He
> Fix For: 2.0.0
>
>
> Currently, if visibility label security is enabled for a HBase instance, after VisibilityController is configured, the cell level visibility label filtering will kick in across the HBase instance.
> Cell level visibility label filtering has non-negligible performance impact.
> On the other hand, in many use cases, only a small portion of the overall data needs visibility label protection.
> If we can support visibility label security at a limited and localized level, we will broaden the use cases and the adoption of this feature.
> We should be able to support visibility label security at per table or per column family level. This is quite common in many other HBase features.
> Cell level visibility label filtering will only be enabled and kick in for the tables or column families that the user designates.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)