[
https://issues.apache.org/jira/browse/NIFI-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176453#comment-15176453
]
ASF GitHub Bot commented on NIFI-1488:
--------------------------------------
Github user rickysaltzer commented on a diff in the pull request:
https://github.com/apache/nifi/pull/253#discussion_r54787933
--- Diff:
nifi-nar-bundles/nifi-standard-services/nifi-hbase-client-service-api/src/main/java/org/apache/nifi/hbase/HBaseClientService.java
---
@@ -40,6 +40,18 @@
.addValidator(new ConfigFilesValidator())
.build();
+ PropertyDescriptor KERBEROS_PRINCIPAL = new
PropertyDescriptor.Builder()
+ .name("Kerberos Principal")
+ .description("Principal of user writing to hbase")
+ .addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
--- End diff --
I believe using the `StandardValidators.NON_EMPTY_VALIDATOR` will cause the
processor to be invalid if we want to talk to a non-secure HBase cluster, since
our principal would be blank/empty.
> 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
> Priority: Minor
>
> 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)
