[ 
https://issues.apache.org/jira/browse/NIFI-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175600#comment-16175600
 ] 

Matt Burgess commented on NIFI-3915:
------------------------------------

As far as I can tell, Kerberos support for Cassandra is only available via a 
vendor (DataStax Enterprise), they have their own fork of the Apache Cassandra 
driver, which does appear to be Apache 2.0-licensed.  However their transitive 
dependencies are of different (older) versions than the current version of the 
driver included with the NiFi Cassandra processors (driver version 3.0.2). I'm 
worried that switching to 1.0.6-dse or some other non-Apache-based version 
could cause problems for those using Apache Cassandra clusters.

Perhaps an initial approach is to parameterize the version for 
cassandra-driver-core in nifi-cassandra-processors/pom.xml. Then, as long as 
the driver is truly a drop-in replacement, you could build the 
nifi-cassandra-bundle overriding that property with a vendor-specific version.  
Having said that, you would also need to add a processor property (to 
AbstractCassandraProcessor) for the JAAS Client App name, and some way to use 
the alternative AuthProvider (perhaps a AuthProvider Class Name property, 
defaulted to empty or the Apache Cassandra default AuthProvider class).  I'm a 
bit leery of adding these properties to Apache NiFi when they can only be used 
with a vendor's product, but there is precedence for it (Shield/X-Pack 
properties for the Elasticsearch processors, e.g.).

Any thoughts on this? I am welcome to all comments, questions and suggestions :)

> Add Kerberos support to the Cassandra processors
> ------------------------------------------------
>
>                 Key: NIFI-3915
>                 URL: https://issues.apache.org/jira/browse/NIFI-3915
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.1.0, 1.1.1
>         Environment: RHEL 7
>            Reporter: RAVINDRA
>            Assignee: Matt Burgess
>
> Currently we use PutCassandraQL processor to persists the in to cassandra
> We have a requirement to kerborize the Cassandra cluster
> Since PutCassandraQL processor does not support kerberos,we are having issues 
> integrating Cassndra from NIFI



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to