Very interesting idea. But it would have to autodetect a stopped processor,
and redirect the success path elsewhere. Is there a way to make that switch
automatic through processor and/or workflow configuration, rather than make
it be a manual change?

On Wed, Feb 15, 2017 at 9:51 AM, Bryan Bende <bbe...@gmail.com> wrote:

> During this time when some of the steps are stopped, could just
> connect your HandleHttpRequest to a different path through the flow
> that returns an unavailable, and then when everything is back to
> normal connect it back to the regular path?
>
>
>
> On Mon, Feb 13, 2017 at 8:15 AM, James McMahon <jsmcmah...@gmail.com>
> wrote:
> > Thank you for replying Bryan. Yes sir, I can elaborate. Applications are
> > trying to post content to my NiFi instance to have it processed to
> > downstream systems. Occasionally there are legitimate reasons why we
> might
> > have the steps stopped. Routine administration, that sort of activity. In
> > such cases - NiFi is up, we still have jetty running, but a processor or
> the
> > processors in a workflow are stopped, isn't there a way to intercept the
> > Http POST request at the jetty server level to send a clean reply, such
> as
> > Unavailable?
> >
> > The software engineers responsible for the POSTing applications are
> asking
> > for this. Apparently it is cleaner and preferred to have their software
> > field a standard Http Reply to their POST than to wait for an indefinite
> > period of time for the equivalent of a timeout error.
> >
> > Thanks again for your help. -Jim
> >
> > On Thu, Feb 9, 2017 at 10:34 AM, Bryan Bende <bbe...@gmail.com> wrote:
> >>
> >> Hello,
> >>
> >> I'm not sure I fully understand the question...
> >>
> >> You would need HandletHttpRequest -> some processors ->
> >> HandleHttpResponse all in a running state in order for someone to
> >> receive a response.
> >>
> >> Can you elaborate on what you are trying to do?
> >>
> >> Thanks,
> >>
> >> Bryan
> >>
> >> On Thu, Feb 9, 2017 at 4:32 AM, James McMahon <jsmcmah...@gmail.com>
> >> wrote:
> >> > Good morning. The first processor in my workflow is a
> HandleHttpRequest.
> >> > How
> >> > do we set up to send a HandleHttpResponse if that processor is stopped
> >> > and
> >> > so not in a running state?
> >> >
> >> > Thank you. -Jim Mc.
> >
> >
>

Reply via email to