Hey Kelsey, we were looking at doing something similar, and like Shawn mentioned, we also implemented RouteonAttribute. We quickly hit some limitations specific to our needs, and decided to just manipulate the flow via the API.
On 27 June 2018 at 14:38, Kelsey RIDER <[email protected]> wrote: > Hello, > > > > I have a project where I’d like NiFi to expose about 4 different RESTful > endpoints. > > The flow behind each of these involves a half-dozen steps and is different > in each case. > > > > I wanted to set it up so that each flow started with a HandleHTTPRequest > processor bound to the appropriate URL path. However, it turns out that two > such processors cannot cohabitate because each one tries to start its own > server bound to the given port. > > I’m wondering: > > - Is there a better way of doing this, without having to have a single > HandleHTTPRequest and making my flows more complicated with all the > required connections to link it to my current entry points? > - Would it be technically possible to have some sort of “HTTPService” > controller that just starts the server and binds to the port, and then > multiple “HTTPServiceListener” processors that use it? Or is it not > possible for a Controller Service to “wake up” a Processor/initiate a flow? > > > > Thanks for the help, > > > > Kelsey > Suite à l’évolution des dispositifs de réglementation du travail, si vous > recevez ce mail avant 7h00, en soirée, durant le week-end ou vos congés > merci, sauf cas d’urgence exceptionnelle, de ne pas le traiter ni d’y > répondre immédiatement. >
