[
https://issues.apache.org/jira/browse/FLINK-18541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18541:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Improvement
> Components: Connectors / ElasticSearch, Table SQL / Ecosystem, Tests
> Reporter: Jark Wu
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
