[
https://issues.apache.org/jira/browse/SAMZA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246667#comment-15246667
]
Jake Maes commented on SAMZA-807:
---------------------------------
Thanks for clarifying, [~zcai]. Isn't is possible to have 2 instances of the
job which don't share a checkpoint topic? Then there shouldn't be an issue.
To be concrete, I'm suggesting to create 2 instances A and B, which either have
different jobName or jobId so that their checkpoint topics are distinct. Then
job A can use org.apache.samza.container.grouper.stream.GroupByPartitionFactory
and job B can use
org.apache.samza.container.grouper.stream.GroupBySystemStreamPartitionFactory
without any conflict.
Would that resolve the issue, or am I misunderstanding the problem?
> Need a configuration variable to ignore SystemStreamPartitionGrouperFactory
> changes in checkpoint topic
> -------------------------------------------------------------------------------------------------------
>
> Key: SAMZA-807
> URL: https://issues.apache.org/jira/browse/SAMZA-807
> Project: Samza
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Tao Feng
> Attachments: SAMZA-807.1.patch
>
>
> We have use cases where the user implemented a customized
> SystemStreamPartitionGrouperFactory and later removed it. We should provide a
> configuration to ignore the validation exception in
> KafkaCheckpointLogKey.fromBytes().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
