Apache Samza 1.3.1 is released

Documentation and Blog are published. See the announcement from samza website and apache blog Thanks, Hai

Re: Samza throwing exception: Duplicate key org.apache.beam.runners.samza.runtime.KeyedTimerData@5a5eb850 registration for the same timer

Hi Sandeep, Thank you for reporting this issue. We noticed this problem during our testing for upcoming Samza release. You can find more details about the bug - https://issues.apache.org/jira/browse/SAMZA-2463 We have a fix and should be included in our upcoming Samza 1.4 release that is slotted

Re: Scaling samza jobs in standalone deployment

app.id is used to identify an instance of your application. Each application consumes all partitions for all topics. With unique app.id , what you really have is two Samza jobs running simultaneously. Sounds to me like what you’re expecting is a single Samza job

[RESULT] [VOTE] Apache Samza 1.3.1 RC0

The vote has passed. Thanks! +1 (binding) x 4: Yi Pan, Bharath, Prateek Maheshwari, Jagadish -- Forwarded message - From: Jagadish Venkatraman Date: Wed, Feb 19, 2020 at 8:32 PM Subject: Re: [VOTE] Apache Samza 1.3.1 RC0 To: dev@samza.apache.org +1 (binding) On Wednesday, Feb

Scaling samza jobs in standalone deployment

Hello Team, I am testing scaling of Samza jobs in standalone deployment model. Jobs are deployed in Kubernetes with zookeeper as job coordinator. The input Kafka topic has two partitions and I am running two Samza instances. The configuration supplied to both instances are identical except app.id,