Adam,
We really should just allow it to be configurable. We tend to be
conservative on such cases but you should have control. Interested in
filing a JIRA?
Thanks
Joe
On Wed, Sep 23, 2015 at 10:01 AM, Adam Williams
wrote:
> I've been playing with the ExtractText
We have already developed modified a modified GetFIle called GetFileData that
takes an incoming FlowFile containing the path to the file/directory that needs
to be transferred. There is a corresponding PutFileData on the other side that
accepts the incoming file/directory that creates the
Worked like a charm! Thank you for your quick response, Daryl and Mark.
The content of the downloaded file is stored in the file generated FlowFile
with a random filename, how would I rename the output file to actual
downloaded filename?
By the way, the ticket is a good enhancement.
Thanks,
Indus,
We should probably have another JIRA to have the InvokeHTTP processor
capture response headers and store them as flow file attributes or at
least as a single attribute with the headers on it - something.
However, the core need you have is totally doable. I'd recommend the
following flow:
Thanks, Joe. That did it, exactly what I was looking for.
You guys and NiFi rock!
On Wed, Sep 23, 2015 at 10:43 PM, Joe Witt wrote:
> Indus,
>
> We should probably have another JIRA to have the InvokeHTTP processor
> capture response headers and store them as flow file
David,
I think if i read your case correctly this should be supported really
well. The flow would be something like:
GetSQS -> SplitJson -> EvaluateJsonPath -> FetchS3Object
In SplitJSON you'll break apart the original object into smaller valid
JSON objects.
In evaluate JsonPath you'll
Bryan - you may be right that ExtractText will be the right play once
splitjson is done doing its thing. Perhaps either will work. Maybe
we can show either or. If the schema is fairly well known i'm
thinking extract json would be the winner.
thanks
Joe
On Wed, Sep 23, 2015 at 4:04 PM, Bryan
Sorry I missed Joe's email while sending mine... I can put together a
template showing this.
On Wednesday, September 23, 2015, Bryan Bende wrote:
> David,
>
> Take a look at ExtractText, it is for pulling FlowFile content into
> attributes. I think that will do what you are
Indus,
As Daryl mentioned, InvokeHTTP will allow you to use the Expression Language to
do an HTTP GET.
It works a bit differently, though, because GetHTTP is a "Source Processor"
whereas InvokeHTTP needs to
be fed a FlowFile to do anything. So you can use GenerateFlowFile as a source
and have
Indus - use InvokeHTTP
Daryl
On Thu, Sep 24, 2015 at 11:07 AM, indus well wrote:
> Hello NiFi Experts:
>
> The GetHTTP processor works fine with static filename when getting files
> from a website. However, I have a use case where I need to download a file
> daily and the
10 matches
Mail list logo