nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-774) Create a DeleteS3Object Processor
Date Thu, 03 Sep 2015 05:02:45 GMT

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

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

Github user taftster commented on the pull request:

    https://github.com/apache/nifi/pull/80#issuecomment-137332775
  
    I'm not sure that checking for the existence of an existing object is that important.
 At minimum, it's causing an extra call to the remote S3 service to determine if the object
exists.  The S3 service itself will not return a different response code if the object previously
existed.
    
    What value is added by having the REL_NOT_FOUND relationship?  What use case is this trying
to solve?
    
    A request to delete an object, regardless of its previous existence, still results in
the same remote state.  HTTP DELETE, being an idempotent method, doesn't really care if the
object existed beforehand or not.



> Create a DeleteS3Object Processor
> ---------------------------------
>
>                 Key: NIFI-774
>                 URL: https://issues.apache.org/jira/browse/NIFI-774
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Yu Ishikawa
>              Labels: amazon, s3
>             Fix For: 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message