7
docs/learn/documentation/0.7.0/yarn/isolation.md
c68572967d42ab9f973e7b62f7c604b07ff5
Diff: https://reviews.apache.org/r/21866/diff/
Testing
---
Thanks,
Martin Kleppmann
Hi all,
Lots of good thoughts here.
I agree with the general philosophy of tying Samza more firmly to Kafka. After
I spent a while looking at integrating other message brokers (e.g. Kinesis)
with SystemConsumer, I came to the conclusion that SystemConsumer tacitly
assumes a model so much like
ourcing Samza,
> however at that time Kafka was relatively unknown and we decided not to do
> it since we felt it would be limiting. From my point of view the three
> things have changed (1) Kafka is now really heavily used for stream
> processing, (2) we learned that abstractin
Hi Shekar,
The store.all() iterator ought to give you the entire contents of the store.
However, note that each partition of the input topic results in a separate
StreamTask instance, which in turn has a separate store. So there will be as
many stores as there are input partitions. Perhaps you'
+1 (binding) on RC1. Verified sig, built, tested with hello-samza.
On 2 Jul 2015, at 19:22, Yi Pan wrote:
> Hi, Jakob,
>
> A quick code search suggests that you were on Kafka. :)
>
> It sounds good to me to extend till 5pm 7/6 for the vote, to count for the
> US holidays. Any objections?
>
>
t;>>>> Logstash is vastly inferior in terms of capabilities to Samza but
>>> it's
>>>> easy
>>>>>>> to get started and that makes a big difference.
>>>>>>>
>>>>>>> Cheers,
>>>>>>
