[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
