[
https://issues.apache.org/jira/browse/NIFI-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187651#comment-15187651
]
ASF GitHub Bot commented on NIFI-1488:
--------------------------------------
Github user lordjc commented on the pull request:
https://github.com/apache/nifi/pull/253#issuecomment-194448347
@alopresto
Thank you for the feedback.
Turning kerberos on and off for a cluster is a non trivial task, but if
that did in fact occur one would need to update all of the configuration files.
"NiFi is started and HBase processor is added and configured to use
Kerberos to connect (processor properties not saved yet, perhaps?)"
This is not a processor but a "service" which gets enabled. In order to
enable it you need to first save the service config. At this point the
ugi.isSecurityEnabled() method would be run and subsequently the validations
would be run to include customValidate.
> Add Kerberos Support to HBase processors
> ----------------------------------------
>
> Key: NIFI-1488
> URL: https://issues.apache.org/jira/browse/NIFI-1488
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.4.0, 0.4.1
> Reporter: Bryan Bende
> Assignee: Ricky Saltzer
>
> Our current HBase integration does not support communicating with a
> Kerberized HBase install. We should support this just like we do for the HDFS
> processors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
