Github user trixpan commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173737898
Is it my impression or this controller is embedding elastic search into
NiFi in order to use the Transport protocol?
Would this cause all sort of issues around versioning? Even logstash moved
the default behaviour from using transport clients into the HTTP bulk api.
Elastic.co is quite explicit in stating the benefits on using the HTTP API:
> This output lets you store logs in Elasticsearch using the native node
and transport
> protocols. It is highly recommended to use the regular
logstash-output-elasticsearch
> output which uses HTTP instead. This output is, in-fact, sometimes
slower, and never
> faster than that one. Additionally, upgrading your Elasticsearch cluster
may require
> you to simultaneously update this plugin for any protocol level changes.
The HTTP
> client may be easier to work with due to wider familiarity with HTTP.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
