Boris,
The ask seems to be for a *change-logged store* + broadcast stream
(basically shared persistent fault-tolerant state across all task
instances).
On Wed, May 4, 2016 at 9:25 AM, Boris Shkolnik wrote:
> I may be missing something - but doesn't that sounds exactly as broadcast
> stream? Y
I may be missing something - but doesn't that sounds exactly as broadcast
stream? You can make all the tasks read from all the partitions.
(
https://samza.apache.org/learn/documentation/0.10/container/samza-container.html,
search for broadcast)
On Tue, May 3, 2016 at 12:46 PM, Jacob Maes wrote:
This sounds like SAMZA-402 (https://issues.apache.org/jira/browse/SAMZA-402)
which, unfortunately, hasn't been implemented yet.
On Tue, May 3, 2016 at 7:48 AM, Bae, Jae Hyeon wrote:
> Can we make a kafka topic as KV store globally to all tasks, not
> partitioned? For example, we have a kafka t
Can we make a kafka topic as KV store globally to all tasks, not
partitioned? For example, we have a kafka topic "cache" and it has a 4
partitions. If we launch a container with 4 tasks, each task will have one
partition of "cache" kafka topic and create a KV store instance. I want to
make all 4 pa
Hi,
What do you mean by broadcasted KV storage? Currently a KV store instance
is specific to a task. Are you referring to broadcast streams?
On Mon, May 2, 2016 at 7:58 PM, Bae, Jae Hyeon wrote:
> Hi Samza devs and users
>
> Is it possible to implement broadcasted KeyValueStorage with 0.9? I
Hi Samza devs and users
Is it possible to implement broadcasted KeyValueStorage with 0.9? I know
0.10 supports broadcast but we're not yet to 0.10.
Thank you
Best, Jae
