[
https://issues.apache.org/jira/browse/BEAM-10838?focusedWorklogId=719034&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-719034
]
ASF GitHub Bot logged work on BEAM-10838:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Feb/22 21:56
Start Date: 01/Feb/22 21:56
Worklog Time Spent: 10m
Work Description: clandry94 commented on a change in pull request #16690:
URL: https://github.com/apache/beam/pull/16690#discussion_r797065234
##########
File path:
sdks/java/io/elasticsearch-tests/elasticsearch-tests-7/src/test/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIOTest.java
##########
@@ -83,6 +83,12 @@ public void setup() throws IOException {
@Rule public TestPipeline pipeline = TestPipeline.create();
+ @Test
Review comment:
It feels wrong making a unit test in this file for the
`SslConfiguration` class as all the other tests in this file are hitting an
Elasticsearch cluster. I don't really have any need to do that here as we know
that the ES client works with a valid SSL config. Really, I just want to test
that SslConfiguration serializes properly and that pipelines still init as
expected.
--
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: 719034)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
