You can have cycles in storm. As an example: Bolt A -> Bolt B
Bolt B -> Bolt C Bolt B (non-default stream) -> Bolt A By using a different stream you can avoid infinite looping. On Tue, Mar 3, 2015 at 12:51 PM, Susheel Kumar Gadalay <[email protected]> wrote: > You want to share some info with the parent bolt means you want to > emit some tuples to the parent bolt. > > Will it not lead to cyclic. > As far as I know it has to DAG (Directed Acyclic Graph). > > On 3/3/15, Ravali Kandur <[email protected]> wrote: > > Sure Vineet, > > > > I have a use case where I need to keep a track of the immediate parent of > > the bolt to convey some information regarding the messages received. > > > > For example, when I receive a message from BoltB to BoltC, once BoltC > > processes the message, it needs to share some information with BoltB > within > > certain time. So, if there is a way in which I can track BoltB, it would > > really help me to solve the problem. > > > > Please let me know if you need more details ! > > > > Regards, > > Ravali Kandur > > > > On Tue, Mar 3, 2015 at 1:50 AM, Vineet Mishra <[email protected]> > > wrote: > > > >> Hi, > >> > >> Could you elaborate your use case for that? > >> > >> On Mon, Mar 2, 2015 at 12:01 PM, Ravali Kandur <[email protected]> > wrote: > >> > >>> Hi, > >>> > >>> > >>> > >>> I was wondering if there is a way to know the details of the > >>> preceding/succeeding bolts information programmatically. > >>> > >>> > >>> > >>> For example, in the image shown below, can I know the information of > >>> *Bolt > >>> B and Bolt D from Bolt D* ? > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> Any help is highly appreciated ! > >>> > >>> > >>> > >>> Regards, > >>> > >>> Ravali Kandur > >>> > >> > >> > > >
