[
https://issues.apache.org/jira/browse/BEAM-10838?focusedWorklogId=757581&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757581
]
ASF GitHub Bot logged work on BEAM-10838:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/22 12:46
Start Date: 16/Apr/22 12:46
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #16690:
URL: https://github.com/apache/beam/pull/16690#issuecomment-1100655923
This pull request has been marked as stale due to 60 days of inactivity. It
will be closed in 1 week if no further activity occurs. If you think that’s
incorrect or this pull request requires a review, please simply write any
comment. If closed, you can revive the PR at any time and @mention a reviewer
or discuss it on the [email protected] list. Thank you for your
contributions.
Issue Time Tracking
-------------------
Worklog Id: (was: 757581)
Time Spent: 1h 40m (was: 1.5h)
> 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 40m
> 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)
