>
> > Yes. The code snippet provided in the email should work as expected.
> >
> > Hope that helps.
> >
> > Thanks,
> > Bharath
> >
> > On Fri, Oct 18, 2019 at 5:55 AM Eric Shieh wrote:
> >
> > > Hi,
> > >
> > > Base
> using Beam API and run it using Samza can be found:
> https://github.com/apache/samza-beam-examples
>
> Please reach out to us if you have more questions.
>
> Thanks,
> Bharath
>
> On Wed, Oct 16, 2019 at 7:31 AM Eric Shieh wrote:
>
> > Thank you Bharath. Rega
Hi,
Based on the source code, it appears that each job designates a unique
group id when subscribing to kafka topic, is my understanding correct? If
so, since one cannot call appDescriptor.getInputStream with the
same KafkaInputDescriptor twice, is it possible to have 2 independent stack
of opera
> *common/shared system services as there is no app or jobper say, I just
> > need to specify the streams and output system*
>
>
> Also, I am not sure I follow what do you mean by "*there is no app or
> job"*.
> You still have 1 app per config + deployment, righ
Hi,
I am new to Samza, I am evaluating Samza as the backbone for my streaming
CEP requirement. I have:
1. Multiple data enrichment and ETL jobs
2. Multiple domain specific CEP rulesets
3. Common/shared system services like consuming topics/streams and
persisting the messages in ElasticSearch and
