That makes sense, thanks!
On Sat, Jan 24, 2015 at 7:00 PM, Jay Kreps wrote:
> But I think the flaw in trying to guess what kind of serializer they will
> use is when we get it wrong. Basically let's say we guess "String". Say 30%
> of the time we will be right and we will save the two configurat
But I think the flaw in trying to guess what kind of serializer they will
use is when we get it wrong. Basically let's say we guess "String". Say 30%
of the time we will be right and we will save the two configuration lines.
70% of the time we will be wrong and the user gets a super cryptic
ClassCa
Maybe. I think the StringSerialzer could look more like a typical type of
message. Instead of encoding being a property it would be more typically
just written in the bytes.
On Sat, Jan 24, 2015 at 12:12 AM, Jay Kreps wrote:
> I don't think so--see if you buy my explanation. We previously defau
Yes, turns out that during the upgrade from CDH5.2 to CDH5.3, the namespace
changed from "/kafka" to simply "/" on Zk. I spoke with the developers over
at Cloudera and they said, using "/" seemed to be the convention. I am
going to open a case with them to clearly document the change so other
custo
Hi all,
I am currently working on logstash to mongodb.logstash's input
(producer) is kafka and output (consumer) is mongodb.It is worked fine for
past two days.Today it is not working and i got the following error.i
googled this error,still didnt find any correct solution.kindly help me to
r
