[
https://issues.apache.org/jira/browse/BEAM-14000?focusedWorklogId=756430&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-756430
]
ASF GitHub Bot logged work on BEAM-14000:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Apr/22 14:22
Start Date: 13/Apr/22 14:22
Worklog Time Spent: 10m
Work Description: nishantjain91 commented on PR #17297:
URL: https://github.com/apache/beam/pull/17297#issuecomment-1098113430
@egalpin I added the unit test case.
At the moment, I added the test case in elasticsearch 7 client, but I think
that might not be appropriate place for this unit test as it does not need to
startup a elasticsearch server in docker to test.
It would be possible to move this test in same package as elasticsearch but
not sure whether that would be correct or not.
COuld you please review it again and let me know if more changes are
required
Issue Time Tracking
-------------------
Worklog Id: (was: 756430)
Time Spent: 1.5h (was: 1h 20m)
> Elastic search IO doesnot work when both username/password and keystore are
> used
> --------------------------------------------------------------------------------
>
> Key: BEAM-14000
> URL: https://issues.apache.org/jira/browse/BEAM-14000
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: nishant jain
> Priority: P2
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When using both username/password and ssl keystore, ElasticSearchIO doesnot
> Create correct restclient.
>
> Firstly, it sets HttpClientConfigCallback using httpAsyncClientBuilder if
> username and passowrd is used. Afterwards, it will replace
> HttpClientConfigCallback to httpClientBuilder is ssl store is used, hence
> losing the credentials provider
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
