[
https://issues.apache.org/jira/browse/FLINK-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu updated FLINK-18541:
----------------------------
Description:
We introduced the authentication feature for Elasticsearch connector in
FLINK-18361, i.e. the {{username}} and {{password}} options. However, it's hard
to test the options in integration test, because the embedded Elasticsearch
cluster doesn't support authentication. Therefore, we would like to verify this
feature in end to end tests.
Before adding the tests, in order to be able to use the new connector options,
we should migrate the existing Elasticsearch e2e to Java testing framework
FLINK-14620.
As a reference about how to configure security:
https://www.elastic.co/guide/en/elasticsearch/reference/7.x/configuring-security.html#configuring-security
was:We introduced the FLINK-18361
> Verify the Elasticsearch authentication option in end to end test
> -----------------------------------------------------------------
>
> Key: FLINK-18541
> URL: https://issues.apache.org/jira/browse/FLINK-18541
> Project: Flink
> Issue Type: Test
> Components: Connectors / ElasticSearch, Table SQL / Ecosystem, Tests
> Reporter: Jark Wu
> Priority: Major
> Fix For: 1.12.0
>
>
> We introduced the authentication feature for Elasticsearch connector in
> FLINK-18361, i.e. the {{username}} and {{password}} options. However, it's
> hard to test the options in integration test, because the embedded
> Elasticsearch cluster doesn't support authentication. Therefore, we would
> like to verify this feature in end to end tests.
> Before adding the tests, in order to be able to use the new connector
> options, we should migrate the existing Elasticsearch e2e to Java testing
> framework FLINK-14620.
> As a reference about how to configure security:
> https://www.elastic.co/guide/en/elasticsearch/reference/7.x/configuring-security.html#configuring-security
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
