Thank you Bharath and Boris, I really appreciate your response and guidance!
Regards,
Eric
On Tue, Oct 22, 2019 at 6:00 PM Boris S wrote:
> Yes, to answer your second question , you should be able to fork the
> streams. Message Streams are idempotent and can be used in different
> pipelines.
>
Yes, to answer your second question , you should be able to fork the
streams. Message Streams are idempotent and can be used in different
pipelines.
With regards to group id, Samza does set the group ids, but, I think, they
are the same for the whole job. The idea behind it is, that Samza is not
u
Hi Eric,
Based on the source code, it appears that each job designates a unique
> group id when subscribing to kafka topic, is my understanding correct?
>
Yes. Samza uses a combination of job name and job id to generate the group
id.
> is it possible to have 2 independent stack
of operations a
Hi Bharath,
Thank you very much, this is extremely helpful! I had not originally
contemplated using beam but will definitely look into it following your
recommendation.
Based on your response and upon further reading of the source code, I
realized my original understanding of the samza-elasticse
Hi Eric,
Thanks for additional clarification. I now have a better understanding of
your use case.
Your use case be accomplished using various approaches.
1. One Samza application that consumes all of your input streams (A and
D) and also your intermediate output streams (B) and routes it t
