[
https://issues.apache.org/jira/browse/NIFI-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630297#comment-15630297
]
ASF subversion and git services commented on NIFI-2834:
-------------------------------------------------------
Commit b5550ffcf5d3b968551b91a41f146b18dcc0a9ec in nifi's branch
refs/heads/master from [~josephxsxn]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b5550ff ]
NIFI-2834 Better Configs for Fetch and Timeout
NIFI-2834 Better Configs for Fetch and Timeout
NIFI-2834 Better Configs for Fetch and Timeout
NIFI-2834 ofSec to of Mils
This closes #1167
> GetAzureEventHub should be more configurable
> --------------------------------------------
>
> Key: NIFI-2834
> URL: https://issues.apache.org/jira/browse/NIFI-2834
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Joseph Niemiec
> Priority: Minor
> Fix For: 1.1.0
>
>
> Current GetAzureEventHub processor is configured to always grab a max batch
> of 100 events per ontrigger[1]. This internal batching scheme should be made
> configurable.
> Also there is an internal default timeout set for PartitionReceivers of 60
> seconds. This means each time the processor is triggered it will be blocked
> waiting for there to be the max number of events (currently 100) before
> canceling 60s later if there isn't 100 events. This should be configurable.
> [1]
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/eventhub/GetAzureEventHub.java#L215
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
