You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Michael Hogue (JIRA)" <ji...@apache.org> on 2017/09/12 19:04:00 UTC

[jira] [Commented] (NIFI-3402) Add ETag Support to InvokeHTTP

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

Michael Hogue commented on NIFI-3402:
-------------------------------------

PR submitted: https://github.com/apache/nifi/pull/2150

> Add ETag Support to InvokeHTTP
> ------------------------------
>
>                 Key: NIFI-3402
>                 URL: https://issues.apache.org/jira/browse/NIFI-3402
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Brandon DeVries
>            Assignee: Michael Hogue
>            Priority: Trivial
>
> Unlike GetHTTP, when running in "source" mode InvokeHTTP doesn't support ETags.  It will pull from a URL as often as it is scheduled to run.  When running with an input relationship, it would potentially make sense to not use the ETag.  But at least in "source" mode, it seems like it should at least be an option.
> To maintain backwards compatibility and support the non-"source" usage, I'd suggest creating a new "Use ETag" property that defaults to false...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)