[
https://issues.apache.org/jira/browse/FLINK-17623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Wang updated FLINK-17623:
-----------------------------
Description:
There should be a way for an [ElasticsearchSinkFunction|#L61]] implementation
to use resources with the same lifecycle as the Elasticsearch sink, for
example, an
[RestHighLevelClient|[https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-high.html]].
Currently there is no way to clean up such resources. This can be achieved by
exposing a `close()` method in the ElasticsearchSinkFunction interface, and
invoke the close method from E[lasticsearchSinkBase.close|#L331].
was:
There should be a way for an [ElasticsearchSinkFunction|#L61]] implementation
to use resources with the same lifecycle as the Elasticsearch sink, for
example, an
[RestHighLevelClient|[https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-high.html]].
Currently there is no way to clean up such resources. This can be achieved by
exposing a `close()` method in the ElasticsearchSinkFunction interface, and
invoke the close method from E[lasticsearchSinkBase.close|#L331]].
> Elasticsearch sink should support user resource cleanup
> -------------------------------------------------------
>
> Key: FLINK-17623
> URL: https://issues.apache.org/jira/browse/FLINK-17623
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch
> Reporter: Yun Wang
> Priority: Major
> Labels: usability
>
> There should be a way for an [ElasticsearchSinkFunction|#L61]] implementation
> to use resources with the same lifecycle as the Elasticsearch sink, for
> example, an
> [RestHighLevelClient|[https://www.elastic.co/guide/en/elasticsearch/client/java-rest/master/java-rest-high.html]].
> Currently there is no way to clean up such resources. This can be achieved by
> exposing a `close()` method in the ElasticsearchSinkFunction interface, and
> invoke the close method from E[lasticsearchSinkBase.close|#L331].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
