Sorry, yes I think it's a blocker. It floods logs for everyone using the spout with autocommit enabled. It would do the same for anyone using the new at-most-once mode.
-1 2018-01-29 9:55 GMT+01:00 Jungtaek Lim <[email protected]>: > I think we didn't decide STORM-2913 as blocker yet, though I agree it is at > least critical as its priority tells. > > Stig, please change priority of issue to 'blocker' and vote to -1 (binding) > if you think the issue is blocker, so that we could decide clearly whether > RC2 should be cancelled or not. Once we started VOTE for RC, I'd like to > see us concerning VOTE first. > The issue should be resolved ASAP (we're only left reviewing) if it is > defined as blocker. > > Taylor, > I guess you're closing the gate and only allowing for blocker issues. Do I > understand correctly? If not, I'd like to merge waiting patches into > 1.x-branch to be included to 1.2.0. > > Thanks, > Jungtaek Lim (HeartSaVioR) > > 2018년 1월 27일 (토) 오후 6:29, Alexandre Vermeerbergen < > [email protected]>님이 > 작성: > > > Hello Stig, > > > > Thank you very much for your answer, I am feeling better now that I > > see that the issue with Storm Kafka Client generating WARN in a loop > > is known and taken as a blocker for 1.2.0 final. > > > > I volunteer to test any binary of storm-kafka-client fixing this > > STORM-2913 issue, if that can hep. > > > > Best regards, > > Alexandre Vermeerbergen > > >
