exceptionfactory commented on PR #7532: URL: https://github.com/apache/nifi/pull/7532#issuecomment-1660373593
Thanks for the reply @pspiller! One other thing to note about HTTP communication in relation to this Processor, often REST services will have separate endpoints for batch processing. This is much more efficient in terms of network communication and transaction handling, but of course it depends on the service in question. Another point to consider is that while InvokeHTTP supports all of the standard HTTP verbs, a record-oriented Processor only seems to make sense in the context of sending a request body, such as with POST, PUT, or PATCH. Given these points, I think it would be best to close the current PR and scope out the options on the Jira issue. With the goal being a generic reusable Processor, it would also be very helpful to highlight some well-known REST services where this proposed Processor would make sense. That would help highlight whether it is a good fit for something generic, or whether it ends up being too complicated for general use. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
