flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Dias (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-4885) Improve the Elasticsearch configuration flexibility
Date Tue, 01 Nov 2016 03:17:58 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Dias closed FLINK-4885.
----------------------------
    Resolution: Invalid

I just realized that these optimizations aren't doable because:
 - The missing constructor was intentionally removed due Jar Hell issues mentioned in the
ES 2.x PR (https://github.com/apache/flink/pull/1792)
 - The {{Client}} instance is not serializable, so it cannot be a non-transient field  of
{{RichSinkFunction}}

> Improve the Elasticsearch configuration flexibility
> ---------------------------------------------------
>
>                 Key: FLINK-4885
>                 URL: https://issues.apache.org/jira/browse/FLINK-4885
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming Connectors
>            Reporter: Mike Dias
>            Priority: Minor
>              Labels: elasticsearch, streaming
>
> Right now, it's only possible to use Elasticsearch 2.x through {{TransportClient}} due
a missing constructor. We can improve the Elasticsearch configuration flexibility with the
following actions:
>  - Add the missing constructor that was present in Elasticsearch 1.x.
>  - Add another constructor that receives an already configured instance of {{Client}}
by the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message