GitHub user alourie opened a pull request:
https://github.com/apache/zeppelin/pull/2238
0.7.1 with ssl
### What is this PR for?
The Cassandra Interpreter does not support talking to clusters that use
SSL/client to node encryption. It does not have the properties needed to
configure the SSL Context. This PR adds the properties to the driver config and
sets up the SSL options when they are requested.
### What type of PR is it?
Feature
### What is the Jira issue?
[ZEPPELIN-1501](https://issues.apache.org/jira/browse/ZEPPELIN-1501)
### How should this be tested?
Using Cassandra/CQL interpreter connect to a Cassandra cluster that uses a
client to node encryption, i.e:
```
%cassandra
describe keyspaces;
```
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Yes.
The new SSL-related properties should be added to the list
(cassandra.ssl.enabled, cassandra.ssl.truststore.path and
cassandra.ssl.truststore.password).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/instaclustr/zeppelin 0.7.1-withSSL
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2238.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2238
----
commit 521b2d9439277605c957f29e8ba1832ab5a6b4b9
Author: Robert Marshall <robertmarshall@instaclustrs-macbook-pro.local>
Date: 2016-09-18T23:41:23Z
Add SSL support to Cassandra interpreter
commit 1ea328b17dd4ae1dffc06b4be0e37e02886fd41c
Author: Alex Lourie <djay...@gmail.com>
Date: 2017-04-10T01:42:23Z
Simplify const
Signed-off-by: Alex Lourie <djay...@gmail.com>
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
