[
https://issues.apache.org/jira/browse/FLINK-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mingleizhang updated FLINK-7573:
--------------------------------
Description:
Currently, all connectors as far as I have known that merely support the TCP
transport protocol of Elasticsearch, but some of company's ES cluster just
relies on the HTTP protocol, and close the TCP port on production environment.
So, I suggest add a new implemention for creating a HTTP protocol by using
{{JestClient}}, which is a Java HTTP Rest client for ElasticSearch.
FYI
I used 9300 port to access ES cluster. It is really awful and scared. Because
program can not run on a production environment based on a {{TransportClient}}.
So, I have to access the ES cluster by 9200 port instead.
was:Currently, all connectors as far as I have known that merely support the
TCP transport protocol of Elasticsearch, but some of company's ES cluster just
relies on the HTTP protocol, and close the TCP port on production environment.
So, I suggest add a new implemention for creating a HTTP protocol by using
{{JestClient}}, which is a Java HTTP Rest client for ElasticSearch.
> Introduce Http protocol connector for Elasticsearch2
> ----------------------------------------------------
>
> Key: FLINK-7573
> URL: https://issues.apache.org/jira/browse/FLINK-7573
> Project: Flink
> Issue Type: Improvement
> Components: ElasticSearch Connector
> Reporter: mingleizhang
>
> Currently, all connectors as far as I have known that merely support the TCP
> transport protocol of Elasticsearch, but some of company's ES cluster just
> relies on the HTTP protocol, and close the TCP port on production
> environment. So, I suggest add a new implemention for creating a HTTP
> protocol by using {{JestClient}}, which is a Java HTTP Rest client for
> ElasticSearch.
> FYI
> I used 9300 port to access ES cluster. It is really awful and scared. Because
> program can not run on a production environment based on a
> {{TransportClient}}. So, I have to access the ES cluster by 9200 port instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
