[
https://issues.apache.org/jira/browse/FLINK-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153058#comment-16153058
]
mingleizhang commented on FLINK-7573:
-------------------------------------
Hi, [~tzulitai] I guess you should be more familiar with this module. Could you
take a look on this ? I found {{createClient}} in
{{Elasticsearch2ApiCallBridge}} is hardcoded by a {{TransportClient}}, and it
is based on the TCP transport protocol. It is also appear in
{{Elasticsearch5ApiCallBridge}}. I have some idea in my mind, either rename
{{Elasticsearch2ApiCallBridge}} to {{Elasticsearch2ApiCallBridgeByTcp}} or
something like that, or create a new class that implement
{{ElasticsearchApiCallBridge}} interface for supporting create a client based
on JestClient. What do you think of them ? It would be great if you can improve
my mind.
> 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)
