[GitHub] [nifi] ChrisSamo632 commented on pull request #7532: NIFI-7505 Add InvokeHTTPRecord processor

["ChrisSamo632 (via GitHub)" <gi...@apache.org>]

ChrisSamo632 commented on PR #7532:
URL: https://github.com/apache/nifi/pull/7532#issuecomment-1670358882

   One could consider the PutElasticsearchRecord processor as a service/application-specific instance of this - operations are executed per-Record based upon processor properties and/or fields set within Records
   
   For example, the Index Operation (index, update,  delete) can be set based upon a Record field. Similar options are available for other parameters in the Elasticsearch _bulk API call. These settings dictate the body of the request passed to Elasticsearch
   
   A similar approach could be considered here, i.e. allow a Record Path property to set the request Verb based on the value of a field within each Record. In not, however, all that used to using InvokeHTTP, so such an approach may not be so relevant at such a generic level


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org