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

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

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

    https://github.com/apache/nifi/pull/1888#discussion_r124067647
  
    --- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/sqs/DeleteSQS.java
 ---
    @@ -45,7 +46,8 @@
     public class DeleteSQS extends AbstractSQSProcessor {
     
         public static final PropertyDescriptor RECEIPT_HANDLE = new 
PropertyDescriptor.Builder()
    -            .name("Receipt Handle")
    +            .name("sqs-receipt-handle")
    --- End diff --
    
    @jvwing 
    
    I think changing the name attribute at this point will break existing flows.


> DeleteSQS Throws Exception Deleting Message
> -------------------------------------------
>
>                 Key: NIFI-4015
>                 URL: https://issues.apache.org/jira/browse/NIFI-4015
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: James Wing
>            Assignee: James Wing
>            Priority: Minor
>
> While attempting to delete a message from an SQS queue, DeleteSQS throws the 
> following exception:
> {quote}
> DeleteSQS[id=6197f269-015c-1000-9317-818c01162722] Failed to delete 1 objects 
> from SQS due to com.amazonaws.services.sqs.model.AmazonSQSException: The 
> request must contain the parameter DeleteMessageBatchRequestEntry.1.Id. 
> (Service: AmazonSQS; Status Code: 400; Error Code: MissingParameter; Request 
> ID: eea76d96-a07d-5406-9838-3c3f26575223): 
> com.amazonaws.services.sqs.model.AmazonSQSException: The request must contain 
> the parameter DeleteMessageBatchRequestEntry.1.Id. (Service: AmazonSQS; 
> Status Code: 400; Error Code: MissingParameter; Request ID: 
> eea76d96-a07d-5406-9838-3c3f26575223)
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to