Ryan, I don't think anyone has ever created a DeleteS3Object. I created a ticket for it https://issues.apache.org/jira/browse/NIFI-774
Thanks -Mark ---------------------------------------- > Date: Fri, 17 Jul 2015 14:57:58 -0400 > Subject: Re: Amazon S3 Processor > From: [email protected] > To: [email protected] > > I see a PutS3Object and a FetchS3Object.. Is there a way to delete from the > S3 bucket? > > On Fri, Jul 17, 2015 at 9:28 AM, Bryan Bende <[email protected]> wrote: > >> Wiki page started here: >> https://cwiki.apache.org/confluence/display/NIFI/Registry+Design >> >> >> On Fri, Jul 17, 2015 at 7:47 AM, Mark Payne <[email protected]> wrote: >> >>> So I certainly added some AWS processors quite a while back, but clearly >>> they are not there. >>> I think I must have messed up when I merged the branch back into develop >>> and accidentally didn't merge >>> the assembly's pom properly. We should certainly spend some time testing >>> these before the next >>> release though, just to make sure that they are in good working >> condition, >>> since I haven't touched >>> them in a while. And I'm guessing nobody else has, either, given that >> they >>> aren't in the build :) >>> >>> Thanks >>> -Mark >>> >>> ---------------------------------------- >>>> Date: Thu, 16 Jul 2015 22:09:40 -0400 >>>> Subject: Re: Amazon S3 Processor >>>> From: [email protected] >>>> To: [email protected] >>>> CC: [email protected] >>>> >>>> Ryan, >>>> >>>> You are right, what I was trying to say was that there is in fact an >> aws >>>> processor bundle, but it is not being included in the distribution >> right >>>> now. I'm assuming this was not intentional and we would want to correct >>>> this and have it included in the next release, I created a Jira: >>>> >>>> https://issues.apache.org/jira/browse/NIFI-770 >>>> >>>> In the meantime, if you wanted to use those processors, you could >>> download >>>> the nar from the link I provided and place it in the nifi lib directory >>> and >>>> restart nifi, after that you should see them in the UI. The link was >> for >>>> the aws bundle that goes with nifi 0.1.0-incubating. I'm expecting >> there >>>> would be an 0.2.0-incubating version of that nar available through >> Maven >>>> central tomorrow, but not 100% sure about this. >>>> >>>> -Bryan >>>> >>>> On Thu, Jul 16, 2015 at 9:51 PM, Ryan Hendrickson < >>>> [email protected]> wrote: >>>> >>>>> I pulled down the 0.2.0 version tonight... the processors weren't in >> the >>>>> gui/canvas list when I checked. >>>>> >>>>> >>>>> >>> >> https://www.apache.org/dyn/closer.cgi?path=/incubator/nifi/0.2.0-incubating/nifi-0.2.0-incubating-bin.tar.gz >>>>> >>>>> On Thu, Jul 16, 2015 at 9:45 PM, Bryan Bende <[email protected]> >> wrote: >>>>> >>>>>> At first glance it looks like the assembly is not bringing in the >>>>>> nifi-aws-bundle, but the bundle is available: >>>>>> >>>>>> >>>>>> >>> >> http://central.maven.org/maven2/org/apache/nifi/nifi-aws-nar/0.1.0-incubating/nifi-aws-nar-0.1.0-incubating.nar >>>>>> >>>>>> I assume the 0.2.0-incubating version of that would work tomorrow >> when >>>>>> the release is fully pushed out. >>>>>> >>>>>> On Thu, Jul 16, 2015 at 9:27 PM, Joe Witt <[email protected]> >> wrote: >>>>>> >>>>>>> ...these are great points. I feel a cm issue coming... >>>>>>> On Jul 16, 2015 9:07 PM, <[email protected]> wrote: >>>>>>> >>>>>>>> Ryan, >>>>>>>> >>>>>>>> I thought there was an S3 processor too! I also thought I saw a SQS >>>>>>>> processor. Has anyone actually started porting the Amazon SDK over? >>> Our >>>>>>>> inquiring minds want to know... >>>>>>>> >>>>>>>> Adam >>>>>>>> >>>>>>>>> On Jul 16, 2015, at 9:04 PM, Ryan Hendrickson < >>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> I thought there was an Amazon S3 Processor.. I dug around the Jira >>>>>>>>> Issues.. Looks like one was discussed: >>>>>>>>> https://issues.apache.org/jira/browse/NIFI-25 >>>>>>>>> >>>>>>>>> Although I don't see it in 0.2.0, or 0.1.0... Am I missing >>>>>>> something >>>>>>>>> simple here, like an extra nar for extensions? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Ryan >>>>>>>>> >>>>>>>>> --bcaec53d5dfbf617f5051b07c38e-- >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>> >>> >>
