[
https://issues.apache.org/jira/browse/FLINK-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10015:
-----------------------------------
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.
> Use Elasticsearch's ESIntegTestCase to rework 5.x and 6.x's ITCases
> -------------------------------------------------------------------
>
> Key: FLINK-10015
> URL: https://issues.apache.org/jira/browse/FLINK-10015
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch, Tests
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Elasticsearch provides a {{ESIntegTestCase}} base class that provides the
> functionality to write integration tests against an Elasticsearch node:
> https://www.elastic.co/guide/en/elasticsearch/reference/current/integration-tests.html
> Our current Elasticsearch integration tests still test against an embedded
> Elasticsearch node (i.e., directly instantiating an Elasitcsearch {{Node}}),
> and is an usage pattern that Elasticsearch is suggesting against since 5.x.
> We should look into the possibility of using {{ESIntegTestCase}} instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
