---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36163/#review90906
---
samza-api/src/main/java/org/apache/samza/system/SystemAdmin.java
Hi, all,
If there is no objection, I plan to close this vote as passed today. So
far, counting the vote +1 from myself, we have got:
RC1: +1 (binding) x 5 and +1 (non-binding) x2
Thanks!
-Yi
On Tue, Jul 7, 2015 at 11:10 AM, Yi Pan nickpa...@gmail.com wrote:
Hi, all,
Is the vote done? We
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36006/#review90929
---
checkstyle/import-control.xml (line 126)
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35676/#review90976
---
@Naveen, overall looks good. I just have one point in the previous
Good summary Jakob.
WRT to the general purpose vs Kafka-specific, I actually see it slightly
differently. Consider how Storm works as an example, there is a data source
(spout) which could be Kafka, Database, etc, and then there is a transport
(a netty TCP thing iiuc). Storm allows you to process
I'm all for any optimizations that can be made to the Yarn workflow.
I actually agree with Jakob in regard to the producers/consumers. I have
spent sometime writing consumers and producers for other transport
abstractions and overall the current api abstractions in Samza I feel are
pretty good.
Hey, all,
Reviving this thread. It would be really nice if we can update the
Powered-by page when releasing 0.9.1.
Thanks a lot!
-Yi
On Tue, Jun 16, 2015 at 5:31 PM, Chris Riccomini criccom...@apache.org
wrote:
Hey all,
I'm seeing a lot of new faces on the mailing list, which is really
