[
https://issues.apache.org/jira/browse/NIFI-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113553#comment-15113553
]
Joseph Witt commented on NIFI-1431:
-----------------------------------
was just about to ask if caching was in play.
There is presently no way to stop it from honoring the etag/last modified
constructs if a given endpoint supports it. It would be a reasonable option to
make available for people though. It is important to note there is no error to
display. You could, if you wanted to see the bulletin for this and any other
INFO level item of this processor, change the bulletin level on the processor
to INFO.
In the upcoming 050 release we will have a nice framework managed state
mechanism and this sort of caching data should be there as well. If so then
the user will be able to clear state as well.
In your case you might find InvokeHttp to be a better processor for you.
Consider it a more 'raw' HTTP interaction that puts you in total control.
Thanks
Joe
> GetHTTP Breaking after Start/Stop
> ---------------------------------
>
> Key: NIFI-1431
> URL: https://issues.apache.org/jira/browse/NIFI-1431
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.1
> Environment: Ubuntu 14.04 LTS
> Reporter: Aaron Stephens
> Labels: GetHTTP, processor
> Fix For: 0.4.1
>
> Attachments: 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)
