You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2016/01/28 23:26:39 UTC

[jira] [Comment Edited] (NIFI-1431) GetHTTP docs should explain Etag/LastMod support

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

Michael Moser edited comment on NIFI-1431 at 1/28/16 10:25 PM:
---------------------------------------------------------------

I would still like to see ETag tracking an option that you can turn off in a GetHTTP property, but that can be a new Jira ticket.


was (Author: mosermw):
I would still like to see ETag tracking an option that you can turn off in a GetHTTP property, that that can be a new Jira ticket.

> GetHTTP docs should explain Etag/LastMod support
> ------------------------------------------------
>
>                 Key: NIFI-1431
>                 URL: https://issues.apache.org/jira/browse/NIFI-1431
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Documentation & Website, Extensions
>    Affects Versions: 0.4.1
>         Environment: Ubuntu 14.04 LTS
>            Reporter: Aaron Stephens
>            Assignee: Joseph Witt
>            Priority: Minor
>              Labels: GetHTTP, processor
>             Fix For: 0.5.0
>
>         Attachments: 0001-NIFI-1431-Added-documentation-about-how-ETag-and-Las.patch, Screen Shot 2016-01-22 at 8.07.51 PM.png
>
>
> I've ran into a bug where GetHTTP will stop working after the processor has been started and stopped a couple times.  What I mean by "stop working" is that the processor will start the tasks, but no output is ever generated, no errors/warnings, and no FlowFiles show up in Provenance.  The weird thing is that it always works the first time.  Sometimes it breaks after one start/stop, sometimes it lasts two or three cycles.  But the end state is always the same.  The only way I've been able to get around this issue is by deleting and re-creating the processor, or by restarting NiFi completely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)