---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34011/
---
(Updated May 11, 2015, 9:48 a.m.)
Review request for samza.
Changes
---
On May 11, 2015, 1:57 a.m., Chinmay Soman wrote:
gradle/dependency-versions.gradle, line 28
https://reviews.apache.org/r/34011/diff/1/?file=954337#file954337line28
This is kinda surprising. We already have a metricsVersion defined ? I
don't see it being used.
We did but it
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34011/#review83210
---
Thanks for reviewing Chinmay. I will update the diff. Please read
Hi all,
We're planning to have a Samza Job that reads from 2 or more Kafka topics,
the messages are serialized using Binary Json, we'd like to deserialize
each message to its specific Java Type, the job configuration only allows
to declare one system msg deserializer, is there any plan to allow
Hello Dan,
I think your scenario is different with Roger / Garry's. For your case this
is actually the expected behavior since if all brokers are gone at roughly
the same time, and then re-appear with different ip address, then producer
cannot detect the new brokers via metadata refresh since
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34066/
---
(Updated May 12, 2015, 12:08 a.m.)
Review request for samza.
Bugs: SAMZA-662
Do you have control over the binary JSON? If so, perhaps you could
include a discriminator in the JSON itself that allows the deserializer to
target the right output type?
Percy Wegmann
Director, Application Platform Engineering
cell: 512.710.6991
www.evariant.com http://www.evariant.com/
Thanks to both for the responses!
Yi, thanks for pointing that out, I didn't see this before.
systems.system-name.streams.stream-name. samza.msg.serde
That's exactly what I need!
Thanks,
José Luis
On May 11, 2015 6:03 PM, Yi Pan nickpa...@gmail.com wrote:
Hi, Jose,
Please refer to the
