You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/16 16:16:00 UTC
[jira] [Commented] (NIFI-3999) DeleteSQS Should Allow Receipt
Handle Configuration
[ https://issues.apache.org/jira/browse/NIFI-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477658#comment-16477658 ]
ASF subversion and git services commented on NIFI-3999:
-------------------------------------------------------
Commit 10254a03c2127c58d8efc2fecfba3c4e2147143d in nifi's branch refs/heads/master from [~jameswing]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=10254a0 ]
NIFI-4015 NIFI-3999 Fix DeleteSQS Issues
* Avoid exception by providing id in DeleteMessageBatchRequestEntry
* Include receipt handle property descriptor for user configuration
Signed-off-by: Pierre Villard <pi...@gmail.com>
This closes #1888.
> DeleteSQS Should Allow Receipt Handle Configuration
> ---------------------------------------------------
>
> Key: NIFI-3999
> URL: https://issues.apache.org/jira/browse/NIFI-3999
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: James Wing
> Priority: Trivial
>
> DeleteSQS deletes an SQS message identified by its RECEIPT_HANDLE property. However, RECEIPT_HANDLE is not added to the processor to be configured by the user. It works because the default value "$\{sqs.receipt.handle}" matches the attribute written by GetSQS, which is likely the 99% use case. Nonetheless, the property descriptor should be added to processor to make this transparent and optionally configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)