GitHub user echauchot opened a pull request:
https://github.com/apache/beam/pull/3801
ElasticsearchIO: Fix Null Pointer Exception in keystore management
When keystorePath is provided by the user but not keystorePassword, then
keystorePassword == null, generating a Null Pointer Exception
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the
change (usually before you start working on it). Trivial changes like typos do
not require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
- [X] Each commit in the pull request should have a meaningful subject
line and body.
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue.
- [X] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [X] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will be performed on your pull request automatically.
- [X] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
---
R: @jbonofre
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/echauchot/beam ESIO-null-pointer-keystore
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3801.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 #3801
----
commit 0cefc8a189c1178f4d1cb4aa90ee757a9a164a00
Author: Etienne Chauchot <[email protected]>
Date: 2017-09-01T14:31:32Z
ElasticsearchIO: Fix Null Pointer Exception in keystore management
When keystorePath is provided by the user but not keystorePassword, then
keystorePassword == null, generating a Null Pointer Exception
----
---
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.
---
