Github user mattyb149 commented on the pull request:
https://github.com/apache/nifi/pull/180#issuecomment-173769666
You are right that more processing would be needed to coax the flow file
into the right format for the *Http processors. If the ES processors were to
use the HTTP API then it would take care of that for you.
Perhaps the prudent way forward is to get these processors out into the
world (using the Transport client since it's done) and see what the community
thinks. We will eventually have a registry where new versions (and perhaps one
that uses the HTTP API) could be added and the user could select which one(s)
they want. What are your thoughts on this?
---
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.
---
