streamparse: sparse run with named streams not compatible with Storm 1.0.1

Hello,

the currently stable streamparse 3.0.0 is not compatible with Storm 1.0.1, which is the latest official release available on storm.apache.org. It requires at least Storm 1.0.2 or 1.1.0, because FluxShellSpout.setNamedStream and FluxShellBolt.setNamedStream are only available since then.

Since 1.0.2 and 1.1.0 are only released on GitHub and not yet available on maven this might be a serious problem. Streamparse also uses 1.0.1 as a default in the examples.

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 2
Comments: 22 (12 by maintainers)

Most upvoted comments

You need to remove #"org.apache.storm" from jar-exclustions and uberjar-exclusions

tanaysoni on Aug 12, 2016

@piyushchauhan2011 The error you’re seeing is because you don’t have your virtualenv_root set to anything, so it doesn’t know where to create the virtualenv. We really could use some config validation, which is an open issue #173.

dan-blanchard on Aug 12, 2016

Since 1.0.2 is out now and sparse run works with it I suggest to fix the examples / quickstart to use the latest Storm version in the next patch version of streamparse and close this issue when its released.

macheins on Aug 12, 2016

Hello, when going through the wordcount tutorial I am running into this problem: Error: Could not find or load main class org.apache.storm.flux.Flux. Is this related? How can I fix it. I’m new to streamparse and well, not familiar with Java ecosystem at all. Thanks

gwaramadze on Aug 11, 2016