Michael Moser commented on NIFI-3599:

I have an approach to resolve this, but I would like to get [~mcgilman] and/or 
[~scottyaslan] to comment, because there are UI/UX implications.

It's fairly easy to move default back pressure Object and Data Size threshold 
settings from server-side code (StandardFlowFileQueue.java) to nifi.properties 
and make the back end use them.  However, the UI also has default back pressure 
set in the nf-connection-configuration.js code.  The UI does not seem to have 
access to nifi.properties in order to read settings from there.

When a new connection is drawn, I propose setting these two back pressure 
fields to 'default' in the UI, or leave them empty.  If a user doesn't change 
them, the JS would send to the server a null value in the JSON for these two 
fields.  The server would recognize this and use the nifi.properties default 
back pressure settings.  If a user makes changes to these fields, the JSON sent 
to the server would contain those changes.

I tested this approach and it works.  I'll be happy to submit a PR.  But is 
this an acceptable approach?  Thanks for feedback.

> 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: Jeremy Dyer
>            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

Reply via email to