gQ386SnNHjPcwsu4z90mzBkuwoZc6YxOCzMGA0>
From: Prateek Maheshwari
Date: Thursday, March 7, 2019 at 2:57 PM
To: "dev@samza.apache.org" , Jeremiah Adams
Subject: Re: [POSSIBLE PHISHING] Task Partition Commit Failed After Upgrade
Jeremiah, were you able to
Subject: Re: [POSSIBLE PHISHING] Task Partition Commit Failed After Upgrade
Jeremiah, were you able to resolve this issue?
- Prateek
On Wed, Mar 6, 2019 at 10:08 AM Prateek Maheshwari
mailto:prateek...@gmail.com>> wrote:
Hi Jeremiah,
The configuration you want to look for is:
'jo
Jeremiah, were you able to resolve this issue?
- Prateek
On Wed, Mar 6, 2019 at 10:08 AM Prateek Maheshwari
wrote:
> Hi Jeremiah,
>
> The configuration you want to look for is:
> 'job.systemstreampartition.grouper.factory'. It should default to:
> 'org.apache.samza.container.grouper.stream.Grou
Hi Jeremiah,
The configuration you want to look for is:
'job.systemstreampartition.grouper.factory'. It should default to:
'org.apache.samza.container.grouper.stream.GroupByPartitionFactory'.
Can you check if you see this value in the configuration logged by
SamzaContainer during container start?
It appears that the issue is related to the KafkaCheckpointLogKey.java
constructor. grouperFactoryClassName here is null. THe documentation indicates
that task.name.grouper.factory config setting has a default value of
org.apache.samza.container.grouper.task.GroupByContainerCountFactory. I
