I'm not sure what the storm release schedule looks like but this is what I've done internally.
I've forked and patched storm: https://github.com/hiloboy0119/incubator-storm I'm running off the trunk but if you wanted to you can checkout the 0.9.1 tag and cherry-pick in the fix: d9d637eab5f3761a4768fc960b2574d45962b466 There isn't any real good documentation on building a storm release but this is what I've figured out: 1. Clone the repo. 2. cd to incubator-storm 3. mvn clean package 4. cd to incubator-storm/storm-dist 5. mvn package 6. The final zips will be in incubator-storm/storm-dist If that all sounds like a bit much you can switch back to 0mq or wait for 0.9.2 =) On Tue, Mar 4, 2014 at 2:36 AM, Richards Peter <[email protected]>wrote: > Hi Drew, > > Good that you identified the root cause for the issue. > > Our team is planning to migrate to storm 0.9.* series. We are planning to > use Netty as the transport layer. Could you please give us a tentative > release date for the build with this fix? > > Thanks, > Richards Peter. >
