ERROR: DISABLED: Visibility labels feature is not available. I get that in hbase shell for commands like get_auths or add_labels. So one thing I noticed is that when I was hand editing hbase-site.xml in /etc/hbase/conf on all nodes, it had no effect(adding the hfile.format.version and the coprocessors for master and region and yes I did a restart after making the changes) However, when I added the coprocessors through the cloudera UI, hbase didn't start up. I checked the logs and sure enough it was complaining about hfile.format.version needing to be set to 3. The problem now I'm having is that there is no hfile.format.version property to set in the cloudera ui Configuration tab. I'm assuming the clouder UI is modifying an hbase-site.xml file with these values somwhere but obviously not in /etc/hbase/config. ... View more

@Harsh J wrote: Thanks for closing the loop! We do not activate v3 HFiles in CDH5.4 to avoid breaking compatibility/adding additional work for users upgrading from an earlier CDH5 release: https://github.com/cloudera/hbase/commit/c9eb03bbf2c54b8e502feef89a59484bad987ff8 Thanks for your response.  I've only defined the VisibilityController as a coprocessor in my hbase-site.xml, so the ordering is not an issue for me.  Yet the visibility label feature is still disabled for me.  Anything else you can suggest for me to try?  I have set the hfile.format.version property to 3 as well.  I don't have the hbase.superuser property defined.  I will try setting it but don't know what else I can try.   Thanks again,   Barry ... View more

I too am finding the visibility labels feature is disabled by default.  How do I go about enabling this feature? ... View more