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

ASF GitHub Bot commented on NIFI-1202:
--------------------------------------

Github user ijokarumawak commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/1306#discussion_r112593685
  
    --- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/audit/RemoteProcessGroupAuditor.java
 ---
    @@ -94,7 +94,13 @@
                         .setConvertName(PORT_NAME_CONVERT),
                 new ConfigurationRecorder<RemoteGroupPort, 
RemoteProcessGroupPortDTO>("Compressed",
                         dto -> dto.getUseCompression() != null, 
RemoteGroupPort::isUseCompression)
    -                    .setConvertName(PORT_NAME_CONVERT)
    +                    .setConvertName(PORT_NAME_CONVERT),
    +            new ConfigurationRecorder<RemoteGroupPort, 
RemoteProcessGroupPortDTO>("Batch Count",
    --- End diff --
    
    Yes, we should. I forgot to use the name converter. Thanks! Fixed this and 
related unit test.


> Allow user to configure Batch Size for site-to-site
> ---------------------------------------------------
>
>                 Key: NIFI-1202
>                 URL: https://issues.apache.org/jira/browse/NIFI-1202
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Core UI, Documentation & Website
>            Reporter: Mark Payne
>            Assignee: Koji Kawamura
>         Attachments: configure-remote-port-window.png, 
> WIP-added-batch-settings-ui.png
>
>
> Currently, there is no way for a user to specify the batch size that 
> Site-to-Site will use. The framework decides this for you. However, if we 
> want to use the List/Fetch Pattern, it will be helpful to specify a small 
> batch size so that a small number of things that are listed are still well 
> distributed across the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to