You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/31 17:31:51 UTC

[jira] (FLINK-4988) Elasticsearch 5.x support

    [ https://issues.apache.org/jira/browse/FLINK-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847173#comment-15847173 ] 

ASF GitHub Bot commented on FLINK-4988:
---------------------------------------

Github user tzulitai commented on the issue:

    https://github.com/apache/flink/pull/3112
  
    While rebasing #2861 on the restructured ES connectors in this PR, I jumped around different options on whether or not the `BulkProcessor` build process should be abstracted. In the end, I think it will still be best to keep that abstracted to keep duplicated code to the minimum.
    
    To bridge the error logging problem, I introduced a `ElasticsearchApiCallBridge` interface to solve this. This call bridge can be further extended for other incompatible APIs that we bump into in the future.


> Elasticsearch 5.x support
> -------------------------
>
>                 Key: FLINK-4988
>                 URL: https://issues.apache.org/jira/browse/FLINK-4988
>             Project: Flink
>          Issue Type: New Feature
>          Components: Streaming Connectors
>            Reporter: Mike Dias
>
> Elasticsearch 5.x was released: https://www.elastic.co/blog/elasticsearch-5-0-0-released



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)