[
https://issues.apache.org/jira/browse/NIFI-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-1130.
------------------------------------
Resolution: Fixed
The {{Max Idle Connections}} property implemented in NIFI-7393 enabled
configurable connection pooling with OkHttp.
> InvokeHttp option to reuse connections
> --------------------------------------
>
> Key: NIFI-1130
> URL: https://issues.apache.org/jira/browse/NIFI-1130
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joe Percivall
> Priority: Minor
>
> The original ticket for this was a collections of improvements to InvokeHttp
> but it was out the scope of the ticket. The original wording is:
> Configuration option for the number of files pulled from the queue at a time
> What this is asking for is a way to reuse connections. This is a bit
> different when we use OkHttp vs HttpUrlConnection and was much more important
> to HttpUrlConnection because it was slower. One challenge facing this is that
> some of the processor properties relating to the connection rely on FlowFile
> attributes so the connection could change in the middle of processing a
> queue.
> If we did this the user would need to be aware that if I problem came up in
> the middle of processing a batch the non-idempotent actions that occured
> outside of NiFi can't be rolled back.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
