[
https://issues.apache.org/jira/browse/NIFI-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395645#comment-16395645
]
ASF GitHub Bot commented on NIFI-3599:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2497
@mosermw @markap14 It's kind of a gray area. I suggested an endpoint like
the /nifi-api/flow/about because that seemed like the best fit currently and
was obviously trying to avoid requiring another request to load the UI. I'm a
little hesitant to go the route of a /nifi-api/flow/properties endpoint because
I'm not sure that's a concept we want to advertise/expose. I don't mind doing
something more generic, but what if the concept was more related to default
values or config. This is something that any client using the API may want to
know ahead of time for this reason exactly. Would adding a DefaultsDTO or
ConfigDTO which is set on the AboutDTO fit a little better?
> Add nifi.properties value to globally set the default backpressure size
> threshold for each connection
> -----------------------------------------------------------------------------------------------------
>
> Key: NIFI-3599
> URL: https://issues.apache.org/jira/browse/NIFI-3599
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Reporter: Jeremy Dyer
> Assignee: Michael Moser
> Priority: Major
>
> By default each new connection added to the workflow canvas will have a
> default backpressure size threshold of 10,000 objects. While the threshold
> can be changed on a connection level it would be convenient to have a global
> mechanism for setting that value to something other than 10,000. This
> enhancement would add a property to nifi.properties that would allow for this
> threshold to be set globally unless otherwise overridden at the connection
> level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
