You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/11/15 13:48:00 UTC

[jira] [Commented] (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=17443826#comment-17443826 ] 

ASF subversion and git services commented on NIFI-830:
------------------------------------------------------

Commit 6fd1f03bd63d41b9c5105a458eb7d81e8ae79700 in nifi's branch refs/heads/main from Nandor Soma Abonyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6fd1f03 ]

NIFI-830 Added FlowFile Naming Strategy to InvokeHTTP

This closes #5475

Signed-off-by: David Handermann <ex...@apache.org>


> 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
>            Assignee: Nandor Soma Abonyi
>            Priority: Minor
>              Labels: beginner, newbie
>         Attachments: 0001-NIFI-830-core-attribute-flowfileName-will-be-last-se.patch
>
>          Time Spent: 7h 10m
>  Remaining Estimate: 0h
>
> 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
(v8.20.1#820001)