[
https://issues.apache.org/jira/browse/NIFI-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988396#comment-14988396
]
Adam Lamar commented on NIFI-1103:
----------------------------------
[~mosermw] I think I share your view as well. I didn't consider the thread pool
issue, but I don't think its necessary to change any default behavior.
[~joewitt] I don't mind pulling together a PR at all.
For what its worth, SQS lets you set a default Receive Message Wait Time on the
queue itself, so as it stands now, one could reach the permanently used thread
condition without realizing it.
> Add support for long polling in GetSQS processor
> ------------------------------------------------
>
> Key: NIFI-1103
> URL: https://issues.apache.org/jira/browse/NIFI-1103
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Adam Lamar
>
> The Amazon SQS API supports and recommends long polling to fetch items from
> the SQS queue. This should drastically reduce the number of requests made by
> the GetSQS processor, and will improve fetch latency in many situations.
> More information:
> http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
