flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ant burton <apburto...@gmail.com>
Subject Re: Flink Elastic Sink AWS ES
Date Sat, 26 Aug 2017 22:39:21 GMT
Hi Ted,

Changing the port from 9300 to 9200 in the example you provides causes the error in the my
original message

my apologies for not providing context in the form of code in my original message, to confirm
I am using the example you provided in my application and have it working using port 9300
in a docker environment locally. 

Thanks,

> On 26 Aug 2017, at 23:24, Ted Yu <yuzhihong@gmail.com> wrote:
> 
> If port 9300 in the following example is replaced by 9200, would that work ?
> 
> https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/connectors/elasticsearch.html
<https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/connectors/elasticsearch.html>
> 
> Please use Flink 1.3.1+
> 
> On Sat, Aug 26, 2017 at 3:00 PM, ant burton <apburton84@gmail.com <mailto:apburton84@gmail.com>>
wrote:
> Hello,
> 
> Has anybody been able to use the Flink Elasticsearch connector to sink data to AWS ES.
> 
> I don’t believe this is possible as AWS ES only allows access to port 9200 (via port
80) on the master node of the ES cluster, and not port 9300 used by the the Flink Elasticsearch
connector.
> 
> The error message that occurs when attempting to connect to AWS ES via port 80 (9200)
with the Flink Elasticsearch connector is:
> 
>     Elasticsearch client is not connected to any Elasticsearch nodes!
> 
> Could anybody confirm the above? and if possible provide an alternative solution?
> 
> Thanks you,
> 


Mime
View raw message