[
https://issues.apache.org/jira/browse/FLINK-26281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510376#comment-17510376
]
Alexander Preuss commented on FLINK-26281:
------------------------------------------
Hi [~guoyangze], yes you can use all of the old connector options as we
reverted the table API part to how it was previously. For datastream you can
set connection request timeout, connection timeout and socket timeout instead :)
> Test Elasticsearch connector End2End
> ------------------------------------
>
> Key: FLINK-26281
> URL: https://issues.apache.org/jira/browse/FLINK-26281
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch
> Affects Versions: 1.15.0
> Reporter: Alexander Preuss
> Assignee: Konstantin Knauf
> Priority: Blocker
> Labels: pull-request-available, release-testing
> Fix For: 1.15.0
>
>
> Feature introduced in https://issues.apache.org/jira/browse/FLINK-24323
> Documentation for [datastream
> api|https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/datastream/elasticsearch/]
> Documentation for [table
> api|https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/elasticsearch/]
> As 1.15 deprecated the SinkFunction-based Elasticsearch connector and
> introduces the new connector based on the Sink interface we should test it
> behaves correctly and as the user expects.
>
> Some suggestions what to test:
> * Test delivery guarantees (none, at-least-once) (exactly-once should not
> run)
> * Write a simple job that is inserting/upserting data into Elasticsearch
> * Write a simple job that is inserting/upserting data into Elasticsearch and
> use a non-default parallelism
> * Write a simple job in both datastream api and table api
> * Test restarting jobs and scaling up/down
> * Test failure of a simple job that is inserting data with exactly-once
> delivery guarantee by terminating and restarting Elasticsearch
> * Test against Elasticsearch 6.X and 7.X with the respective connectors
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
