[
https://issues.apache.org/jira/browse/BEAM-14000?focusedWorklogId=766857&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-766857
]
ASF GitHub Bot logged work on BEAM-14000:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/May/22 18:55
Start Date: 05/May/22 18:55
Worklog Time Spent: 10m
Work Description: egalpin commented on PR #17297:
URL: https://github.com/apache/beam/pull/17297#issuecomment-1118940186
This PR has been blocked on me, apologies for the slow review cadence. The
next step would be to ideally find a way to write a test that "would have
failed" with the code in master now, and would now pass as a result of
@nishantjain91's great changes. That way we can guard against regressions in
the future.
I haven't had time to dig into what options there might be for inspecting
the resulting `RestClient` object (or the effect of the fix on generated
requests via the `RestClient`, which might also be a sufficient test).
Issue Time Tracking
-------------------
Worklog Id: (was: 766857)
Time Spent: 2h 40m (was: 2.5h)
> 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: 2h 40m
> 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.7#820007)
