You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/04/07 07:20:00 UTC
[jira] [Created] (FLINK-17027) Introduce a new Elasticsearch
connector with new property keys
Jark Wu created FLINK-17027:
-------------------------------
Summary: Introduce a new Elasticsearch connector with new property keys
Key: FLINK-17027
URL: https://issues.apache.org/jira/browse/FLINK-17027
Project: Flink
Issue Type: Sub-task
Components: Connectors / ElasticSearch, Table SQL / Ecosystem
Reporter: Jark Wu
Fix For: 1.11.0
This new Elasticsearch connector should use new interfaces proposed by FLIP-95, e.g. DynamicTableSource, DynamicTableSink, and Factory.
The new proposed keys :
||Old key||New key||Note||
|connector.type|connector| |
|connector.version|N/A|merged into 'connector' key|
|connector.hosts|hosts| |
|connector.index|index| |
|connector.document-type|document-type| |
|connector.failure-handler|failure-handler| |
|connector.connection-max-retry-timeout|connection.max-retry-timeout| |
|connector.connection-path-prefix|connection.path-prefix| |
|connector.key-delimiter|document-id.key-delimiter|They can also be used by sources in the future. In addition, we prefix 'document-id' to make the meaning more understandable. |
|connector.key-null-literal|document-id.key-null-literal|
|connector.flush-on-checkpoint|sink.flush-on-checkpoint| |
|connector.bulk-flush.max-actions|sink.bulk-flush.max-actions|we still use bulk-flush, because it's a elasticsearch terminology.|
|connector.bulk-flush.max-size|sink.bulk-flush.max-size| |
|connector.bulk-flush.interval|sink.bulk-flush.interval| |
|connector.bulk-flush.back-off.type|sink.bulk-flush.back-off.strategy| |
|connector.bulk-flush.back-off.max-retries|sink.bulk-flush.back-off.max-retries| |
|connector.bulk-flush.back-off.delay|sink.bulk-flush.back-off.delay| |
--
This message was sent by Atlassian Jira
(v8.3.4#803005)