Hello, If you're using InvokeHttp processor to call REST endpoint, enabling "Always Output Response" might be helpful to generate a FlowFile even if the result HTTP status code is not successful.
Thanks, Koji On Fri, Jan 11, 2019 at 2:31 PM l vic <lvic4...@gmail.com> wrote: > > I have to merge results of "original", REST call and sql query responses > into one flowfile/json.... > The problem happens if REST call, or sql query result in empty resultset. For > example, suppose i have 3 incoming connections for Merge: > original->flowfile1/attribute1, REST->flowfile2/attribute2, SQL > query->flowfile3/attribute3 > If REST call fails (error 404 - record not found), or sql call return empty > resultset - flowfiles never merged ( the origin gets stuck in input queue). > Can I found some merge strategy to solve this problem such as only origin > json would be let through? For example, is there something i can do so that > REST error would result in empty output flowfile? > Thank you...
