[
https://issues.apache.org/jira/browse/FLINK-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336711#comment-17336711
]
Flink Jira Bot commented on FLINK-7573:
---------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Introduce Http protocol connector for Elasticsearch2
> ----------------------------------------------------
>
> Key: FLINK-7573
> URL: https://issues.apache.org/jira/browse/FLINK-7573
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch
> Reporter: zhangminglei
> Priority: Major
> Labels: stale-major
>
> 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. 9300 is for TCP. 9200 is for HTTP for accessing I guess here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
