Created on 02-23-2017 08:41 AM - edited 09-16-2022 04:08 AM
hello,
I am trying to get my CDH 5.9 installation of Hbase working with visibility labels enabled through Cloudera Manager. In the "HBase Service Advanced Configuration Snippet (Safety Valve) for hbase-site.xml" I have set:
After restart, I log in to the Hbase shell and try to "add_labels ['TESTLABEL'] and I am getting the error:
ERROR: DISABLED: Visibility labels feature is not available
Probably something simple that I am missing, but any ideas would be appreciated.
Created 04-26-2017 01:37 PM
For people using Cloudera Manager 5.7+ it also requires adding the following (4th parameter) to the "HBase Service Advanced Configuration Snippet (Safety Valve) for hbase-site.xml" in order to enable visibility labels:
<property>
<name>hbase.security.authorization</name>
<value>true</value>
</property>
So the full list of parameters to enter into the "HBase Service Advanced Configuration Snippet (Safety Valve) for hbase-site.xml" when using Cloudera Manager 5.7+ is as follows:
<property>
<name>hbase.coprocessor.region.classes</name>
<value>org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
</property>
<property>
<name>hbase.coprocessor.master.classes</name>
<value>org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
</property>
<property>
<name>hfile.format.version</name>
<value>3</value>
</property>
<property>
<name>hbase.security.authorization</name>
<value>true</value>
</property>
Customer Operations Engineer
Created 02-23-2017 01:10 PM
Immediately what comes to mind is that there are many safety valves at different scopes of the hbase service.
hbase.coprocessor.region.classes would be scoped to the regionserver safety valve, hbase.coprocessor.master.classes would be scoped to the master safety valve, etc.
additionally you can typically get away with putting things in the service wide safety valve since regionserver won't throw any errors on having hmaster specific config and vice versa. There are obviously cases where you want the same config item to be different for the different services.
you may already know this, but here is the cloudera article on setting this up:
Created 02-24-2017 01:32 AM
Created 03-09-2017 06:50 AM
No joy...I still get this when I do list_labels:
ERROR: DISABLED: Visibility labels feature is not available
Still searching for a (definitive) configuration through Cloudera Manager that will actually turn on visibility labels in HBASE.
Created 04-26-2017 01:37 PM
For people using Cloudera Manager 5.7+ it also requires adding the following (4th parameter) to the "HBase Service Advanced Configuration Snippet (Safety Valve) for hbase-site.xml" in order to enable visibility labels:
<property>
<name>hbase.security.authorization</name>
<value>true</value>
</property>
So the full list of parameters to enter into the "HBase Service Advanced Configuration Snippet (Safety Valve) for hbase-site.xml" when using Cloudera Manager 5.7+ is as follows:
<property>
<name>hbase.coprocessor.region.classes</name>
<value>org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
</property>
<property>
<name>hbase.coprocessor.master.classes</name>
<value>org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
</property>
<property>
<name>hfile.format.version</name>
<value>3</value>
</property>
<property>
<name>hbase.security.authorization</name>
<value>true</value>
</property>
Customer Operations Engineer
Created 04-26-2017 09:26 PM