I agree this is annoying. Do you feel this is a blocker for the 0.8.1 release?. This happens when you kill the console consumer, at the which point you probably won't care what the output is.
On Thu, Mar 6, 2014 at 8:20 AM, Jay Kreps <jay.kr...@gmail.com> wrote: > Do we want to release with this? This basically shows up in the quick start > or any usage. Frankly I would not trust a system that did something like > this under basic usage with my data.... > > -Jay > > > On Tue, Mar 4, 2014 at 9:21 PM, Jun Rao <jun...@gmail.com> wrote: > > > Not sure why the message count output was added. However, it goes to > > stderr, not stdout. > > > > Thanks, > > > > Jun > > > > > > On Tue, Mar 4, 2014 at 8:49 PM, Jay Kreps <jay.kr...@gmail.com> wrote: > > > > > The console consumer broken windows on the 0.8.1 branch. Going through > > the > > > quickstart I notice two issues: > > > > > > 1. Control-C now produces a spurious error message: > > > [2014-03-04 20:44:38,026] WARN Reconnect due to socket error: null > > > (kafka.consumer.SimpleConsumer) > > > > > > 2. Somebody has added this useless message in the output: > > > Consumed 3 messages > > > > > > I actually see 1. in the server logs as well. > > > > > > (2) seems clever but unfortunately with this message you actually can't > > DO > > > anything with the console producer output like pipe it to another > command > > > because we are printing non-message text to the console. Does anyone > know > > > what the motivation for this is? If you want to count the lines just > pipe > > > it to something like wc. This is unix people! > > > > > > -Jay > > > > > >
