GitHub user FireArrow opened a pull request:
https://github.com/apache/zeppelin/pull/1762
[ZEPPELIN-1810] Removed incorrect usage of getString
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://zeppelin.apache.org/contribution/contributions.html
### What type of PR is it?
Hot Fix
### Todos
* [ ] - Task
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1810
### How should this be tested?
Before this fix, after setting `zeppelin.ssl` to true in
`zeppelin-site.xml` and setting `zeppelin.ssl.keystore.path` to a relative path
to a keystore (technically it doens't have to exist at all) and setting
`zeppelin.ssl.truststore.path` to a relative path to a truststore Zeppelin
won't start. In the log you can read something like
```WARN [2016-12-14 13:55:45,522] ({main}
AbstractLifeCycle.java[setFailed]:212) - FAILED
SslContextFactory@8f2098e(/home/firearrow/zeppelin/incubator-zeppelin/conf/null,/home/firearrow/zeppelin/incubator-zeppelin/conf/null):
java.io.FileNotFoundException:
/home/firearrow/zeppelin/incubator-zeppelin/conf/null (No such file or
directory)```
With this fix the correct path is resolved
### Screenshots (if appropriate) N/A
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/FireArrow/zeppelin ZEPPELIN-1810]
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1762.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 #1762
----
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
