[
https://issues.apache.org/jira/browse/BEAM-10838?focusedWorklogId=719257&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-719257
]
ASF GitHub Bot logged work on BEAM-10838:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Feb/22 08:54
Start Date: 02/Feb/22 08:54
Worklog Time Spent: 10m
Work Description: echauchot commented on pull request #16690:
URL: https://github.com/apache/beam/pull/16690#issuecomment-1027713266
@clandry94 thanks for your work !
@egalpin can you take a look ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 719257)
Time Spent: 1h (was: 50m)
> Add a withSSLContext builder method to ElasticsearchIO
> -------------------------------------------------------
>
> Key: BEAM-10838
> URL: https://issues.apache.org/jira/browse/BEAM-10838
> Project: Beam
> Issue Type: New Feature
> Components: io-java-elasticsearch
> Reporter: Conor Landry
> Assignee: Conor Landry
> Priority: P2
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, the ElasticsearchIO transforms have only one way to securely
> read/write Elasticsearch by using the withKeystorePath builder method and
> providing the location of a keystore containing a client key in jks format.
> This is a bit limiting, especially for Elasticsearch users not depending on
> shield to secure their clusters. I'd like to propose the addition of the
> builder method withSSLContext(SSLContext sslContext, which delegates to
> `httpClientBuilder.setSSLContext`.
> If this is (y), I can start working on it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
