[ 
https://issues.apache.org/jira/browse/NIFI-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376856#comment-17376856
 ] 

ASF subversion and git services commented on NIFI-8195:
-------------------------------------------------------

Commit ea31634ea772b7af567a2f2ccb06f7478cff8ecc in nifi's branch 
refs/heads/main from Mark Bean
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ea31634 ]

NIFI-8195: add default connection settings to process group configuration
  - include new process group property support in NiFi Registry
  - updated documentation to describe and show new feature
  - added elements to XSD schema definition

NIFI-8195: update to DAO to fix PG move and copy/paste

update condition to not null vice null

Signed-off-by: Matthew Burgess <[email protected]>

This closes #5192


> Migrate backpressure settings from nifi.properties to Process Group
> -------------------------------------------------------------------
>
>                 Key: NIFI-8195
>                 URL: https://issues.apache.org/jira/browse/NIFI-8195
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Bean
>            Assignee: Mark Bean
>            Priority: Minor
>             Fix For: 1.14.0
>
>          Time Spent: 4h 50m
>  Remaining Estimate: 0h
>
> Currently, there are properties in the nifi.properties file that provide 
> defaults for backpressure limits of newly created connections:
> nifi.queue.backpressure.count=
> nifi.queue.backpressure.size=
> It is a bit heavy-handed to set these at the application level. It would be 
> more appropriate to be configurable at a Process Group level.
> Add configuration properties to the Process Group for these settings. To 
> maintain backward compatibility, the properties may remain in 
> nifi.properties. If provided in nifi.properties, these values would be 
> provided as the default values for newly created Process Groups.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to