Pass full topology information to ShellSpout/ShellBolt#686
Open
mattilyra wants to merge 2 commits intonathanmarz:masterfrom
mattilyra:master
Open
Pass full topology information to ShellSpout/ShellBolt#686mattilyra wants to merge 2 commits intonathanmarz:masterfrom mattilyra:master
mattilyra wants to merge 2 commits intonathanmarz:masterfrom
mattilyra:master
Conversation
… sources and targets of all bolts and spouts.
…e subprocess, and changed storm.py so that the componentId is extracted from setupInfo in initComponent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The subprocesses running under ShellBolt ShellSpout should have information about the topology context they run in, specifically their component ID and the sources and targets.
I think there is already a todo note in GeneralTopologyContext.toJSONString for this.