[
https://issues.apache.org/jira/browse/FLINK-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153064#comment-16153064
]
mingleizhang commented on FLINK-7573:
-------------------------------------
I want to reach an agreement on this issue before start working on this. Like
what is the best way to improve or something like that. As I said before,
{{createClient }} is hardcoded to a {{TransportClient}}. It is not flexible
enough. [~yew1eb] I will be happy if you can give me some idea on this issue. :)
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
