You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Taha Kashaf Haider Naqvi (JIRA)" <ji...@apache.org> on 2018/08/24 06:33:00 UTC

[jira] [Comment Edited] (NIFI-830) For GET requests, InvokeHTTP should set the filename of the 'Response' FlowFile based on the URL

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

Taha Kashaf Haider Naqvi edited comment on NIFI-830 at 8/24/18 6:32 AM:
------------------------------------------------------------------------

Yes it should considered.I will look into this.

So for an operational flow the  same flowFileName would be carried forward unless and until we handle it explicity in 1.X

Can pls share ur operation flow use case.

Thanks.


was (Author: tahakashaf):
Yes it should considered.I will look into this.

So, this can be expected to be introduced in 2.X

It would be a great help if u could share an operational flow.

Thanks.

> For GET requests, InvokeHTTP should set the filename of the 'Response' FlowFile based on the URL
> ------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-830
>                 URL: https://issues.apache.org/jira/browse/NIFI-830
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mark Payne
>            Priority: Minor
>              Labels: beginner, newbie
>         Attachments: 0001-NIFI-830-core-attribute-flowfileName-will-be-last-se.patch
>
>
> When using InvokeHTTP to fetch the content of a particular URL, I expected that the filename of the 'Response' FlowFile would be set to the filename pulled. I.e., if I pulled http://www.somesite.com/images/1.png, I would have expected the 'Response' FlowFile to have a filename of "1.png" but instead it had the same filename as the incoming FlowFile.
> I don't think this is something that we can change until version 1.0.0 because it could potentially break backward compatibility of flows by changing the filename unexpectedly. In the meantime, I have added an UpdateAttribute to set the filename to ${url:substringAfterLast('/'):substringBefore('?')}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)