Getting out a new release for fixing 2682 would be good I think. Regarding other fixes that would be good to get in, I think it would be good to get https://issues.apache.org/jira/browse/STORM-2549, https://issues.apache.org/jira/browse/STORM-2675, https://issues.apache.org/ jira/browse/STORM-2231 fixed.
Alexandre if you are blocked by STORM-2648, why not build storm-kafka-client off of the PR branch? Also I believe that storm-kafka only becomes incompatible with Kafka 1.0.0, it still works for me in tests on an 0.11 broker. 2017-08-25 11:52 GMT+02:00 Alexandre Vermeerbergen <[email protected] >: > Hello, > > Would you please include https://issues.apache.org/jira/browse/STORM-2648 > in upcoming Storm 1.1.2 release : we need to have latency etc stats when > using Storm Kafka Client spout in autocommit mode, not having this feature > is blocking us from moving from old Storm-Kafka lib (limited to Kafka > 0.9.x) to Storm-Kafka-Client lib (required for Kafka 0.10.x compatibility). > > Best regards, > Alexandre > > > > > 2017-08-25 9:26 GMT+02:00 Jungtaek Lim <[email protected]>: > > > Hi devs, > > > > We received a bug report (STORM-2682 > > <https://issues.apache.org/jira/browse/STORM-2682>) on Storm 1.0.4 and > > 1.1.1 which prevents Storm cluster from update. Personally it looks like > > pretty critical, and hopefully it is fixed now. > > So maybe we would like to have another bug fix releases quickly for > > affected 1.x version lines. What do you think? > > > > Also please enumerate the issues if you would want to include any bug fix > > issues to the new bug fix releases, so that we can create epic issues and > > track them to make releases happening sooner. > > > > Thanks, > > Jungtaek Lim (HeartSaVioR) > > >
