[
https://issues.apache.org/jira/browse/NIFI-16113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103382#comment-18103382
]
ASF subversion and git services commented on NIFI-16113:
--------------------------------------------------------
Commit d13701ef26bca8f3d9bb419b184785ecfb0c7860 in nifi's branch
refs/heads/main from pkelly-nifi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d13701ef26b ]
NIFI-16113 Added Processor ChangeSQSMessageVisibilityTimeout for AWS (#11430)
Signed-off-by: David Handermann <[email protected]>
> New processor to change visibility timeouts for SQS messages
> ------------------------------------------------------------
>
> Key: NIFI-16113
> URL: https://issues.apache.org/jira/browse/NIFI-16113
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Paul Kelly
> Assignee: Paul Kelly
> Priority: Minor
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Create a new processor that allows changing the visibility timeout for an SQS
> message. This could be used, for example, when receiving S3 event
> notifications through SQS and fetching the corresponding object from S3.
> Large objects could have their SQS message visibility timeout changed to a
> longer time period to allow for more time downloading, while smaller files
> could objects could use a shorter visibility timeout to allow for faster
> retries. This would allow for more efficient data flows of mixed object
> sizes while minimizing the necessary retry period, rather than using a static
> retry window for all objects.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
