On Tue, Jan 12, 2016 at 7:20 PM, Adam Lamar wrote:
> Russell,
>
> Sorry - I meant that I use the FetchS3Object processor, not ListS3.
Ah, that makes more sense, thanks.
> You can
> set the Object Key property with the name of the key you want to download.
> This property
Hello Russell,
Sorry if that seemed short, I was running in to pick my son up from
my practice. What I meant to say was that you are correct. Although I
haven't worked on those processors, I do believe it is expecting the listS3
processor to function and that is why you are getting that
Russell,
Sorry - I meant that I use the FetchS3Object processor, not ListS3. You
can set the Object Key property with the name of the key you want to
download. This property supports the expression language, so the object
key can be sourced from each flowfile.
I'm unsure if there is a good
Russell/Corey,
In 0.4.0 there is a new way for processors to indicate what they expect as
far as input, it can be required, allowed, or forbidden. This prevents
scenarios like ExecuteSQL which at one point required an input FlowFile,
but the processor could be running and started with out an
I haven't worked with this processor but I believe it is looking for
the S3 list processor to generate the list of objects to fetch. Did
you try that yet?
Sent from my iPhone
> On Jan 12, 2016, at 8:38 PM, Russell Whitaker
> wrote:
>
> I'm running v0.4.1 Nifi, and
On Tue, Jan 12, 2016 at 6:02 PM, Corey Flowers wrote:
> I haven't worked with this processor but I believe it is looking for
> the S3 list processor to generate the list of objects to fetch. Did
> you try that yet?
>
I mentioned this: "There's no "ListS3Object" processor
Ha ha! Well that would do it! :)
Sent from my iPhone
> On Jan 12, 2016, at 9:10 PM, Russell Whitaker
> wrote:
>
>> On Tue, Jan 12, 2016 at 6:02 PM, Corey Flowers
>> wrote:
>> I haven't worked with this processor but I believe it is looking
On Tue, Jan 12, 2016 at 6:11 PM, Corey Flowers wrote:
> Ha ha! Well that would do it! :)
>
I don't know what that would "do" other than confirm that the
FetchS3Object processor shipped
with v0.4.1 needs its doc to reflect the fact it's not yet useable
untl a ListS3*