You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/07/05 14:49:27 UTC

[GitHub] [nifi] MikeThomsen commented on issue #2861: NIFI-5248 Added new Elasticsearch json and record processors.

MikeThomsen commented on issue #2861: NIFI-5248 Added new Elasticsearch json and record processors.
URL: https://github.com/apache/nifi/pull/2861#issuecomment-508782846
 
 
   @mattyb149 I think I get can get these done today. Broadly, my purpose in creating these was to give us a clean path forward to start walking lock step with Elastic on the evolution of their products by doing things like using their APIs, following the newer practice of using controller services to configure connections, etc. One key difference between the two record processors is that this one enables the user to combine together operations against an index beyond "index" type commands. You can, for instance, multiplex index, update and delete against the same index or really as many indices as you want with this because it really is just exposing the bulk api through our record api.
   
   In the long run, I'd like to see the "REST API" bundle become the consolidated path forward with the others deprecated and supported only with emergency patches. As far as I know, they have none of the Elastic features we need like automatic master detection (both on start and change).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services