flux
flux copied to clipboard
Framework for creating and deploying Apache Storm Topologies
In other words, to go in reverse? Thanks in advance!
I'm finding Flux Core declares commons-cli as a dependency... ``` [INFO] +- org.apache.storm:flux-core:jar:0.10.0-beta1:compile [INFO] | \- commons-cli:commons-cli:jar:1.2:compile ``` However the commons-cli packages are in the shaded flux-core.jar as well... ```...
When specifying a component such as **myComponent** in the following config yaml: ``` yaml - components - id: "referencedComponent" className: "com.test.Foo" ... - id: "myComponent" className: "com.test.MyClass" constructorArgs: - [...
Add java annotations that allow users to mark classes/methods as Storm-enabled.
Currently, flux expects a happy path, and doesn't do much in terms of error checking the supplied YAML file. It will validate the topology thrift structure, if it gets that...
Right now includes are only single-level. We should allow them to be recursive.
Currently, we only support YAML topology definitions. The actual YAML parsing code is only a few lines long. It wouldn't be hard to add JSON parsing as well. We could...
Allow users to define trident topologies with YAML/JSON