[
https://issues.apache.org/jira/browse/MINIFICPP-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Szasz updated MINIFICPP-2485:
------------------------------------
Description:
We rely on a fixed URL to have a pool of connections with HTTP Keep-Alive. If
we added Expression Language support to Request URL, we would need to choose:
# Check that the host is unchanged between flow files. This retains the
performance benefits of keep-alive, if the EL expression doesn't influence the
host part.
# Keep a pool of connections associated to each destination host, and throw
away the last used destination host connections when the pool grows above the
limit. This way we can use keep-alive with multiple destination hosts, up to
the limit of the pool times the concurrency of InvokeHTTP.
# Don't reuse connections when EL is involved. This is the simplest fix, but
it sacrifices performance.
> InvokeHTTP: "Request URL" doesn't actually support Expression Language
> ----------------------------------------------------------------------
>
> Key: MINIFICPP-2485
> URL: https://issues.apache.org/jira/browse/MINIFICPP-2485
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Marton Szasz
> Priority: Major
>
> We rely on a fixed URL to have a pool of connections with HTTP Keep-Alive. If
> we added Expression Language support to Request URL, we would need to choose:
> # Check that the host is unchanged between flow files. This retains the
> performance benefits of keep-alive, if the EL expression doesn't influence
> the host part.
> # Keep a pool of connections associated to each destination host, and throw
> away the last used destination host connections when the pool grows above the
> limit. This way we can use keep-alive with multiple destination hosts, up to
> the limit of the pool times the concurrency of InvokeHTTP.
> # Don't reuse connections when EL is involved. This is the simplest fix, but
> it sacrifices performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
