Why would it need its own materializer? On Fri, Nov 4, 2016 at 1:26 PM, Eugene Dzhurinsky <[email protected]> wrote:
> More I think about is - more I am convinced that this is something that > must be implemented via nested flows, like - the step to extract the > initial user profile and then extract all associated records must be > implemented as a separate Graph, that is invoked as part of transformation > of the input stream. > > So I have a flow nested in another flow with it's own materializer - on > every user ID from the outer flow I spawn another instance of inner flow > and wait until it completes, and then send the data down to the appropriate > sinks. > > Am I missing something? > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/c > urrent/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Cheers, √ -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
