I have an very early version of streaming in Kafka I will not be able
to respond back for the next nine days because of no internet connectvity..
But the early version (0.0.1) streams events to browser as events become
available.
www.github.com/milindparikh/streamkl
Regards
Milind
On Fri,
I'm not exactly sure about why talking the same at the wire level is an
explicit goal; if raw blazing speed is also equally important.
Removing the wireformat from Kafka could be done through abstraction; but
that would incur reinterpretation costs(talking native Kafka) and take a
performance hit
information about which topic-partition did this message
originate from is missing in the response?
Is there a JIRA that is getting worked?
Thanks
Milind
On Fri, Sep 28, 2012 at 2:38 PM, Milind Parikh wrote:
> What is the wire format for MULTI-FETCH *RESPONSE* *given
>
>*that t
What is the wire format for MULTI-FETCH *RESPONSE* *given
*that the SINGLE-FETCH RESPONSE LOOKS like this:
RESPONSE_HEADER
ResponseLength:32/integer
ErrorCode:16/integer
MESSAGES
As you may know, we are working on Countandra to be a Apache WHIRR service.
Now that Kafka is integrated into Countandra, I would like to know if Kafka
would also be a WHIRR Service. If so, when?
Thanks
Milind
>From the printed usage pattern --> "--sync
If set message send requests to the
brokers are synchronously, one at
a
time as they arrive. "
seems to imply that the ConsoleProducer by default is sending messages to
t
: Kafka
Issue Type: Bug
Components: contrib
Affects Versions: 0.7
Environment: Ubuntu 10.04, openjdk1.6 with default installation of 0.7
Reporter: milind parikh
Priority: Minor
1. While the default console-producer, console-consumer paradigm
I am experimenting with Kafka to see if it can serve as a event buffer for
Countandra (www.countandra.org) and beyond that, into cascading counters. I
have setup Kafka on a local server Ubuntu 10.04, openjdk1.6 with default
installation of 0.7.
*1. While the default console-producer, console-consu
