[
https://issues.apache.org/jira/browse/BEAM-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174738#comment-17174738
]
Beam JIRA Bot commented on BEAM-7059:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> SamzaRunner: fix the job.id inconsistency in the new Samza version
> ------------------------------------------------------------------
>
> Key: BEAM-7059
> URL: https://issues.apache.org/jira/browse/BEAM-7059
> Project: Beam
> Issue Type: Bug
> Components: runner-samza
> Reporter: Xinyu Liu
> Priority: P2
> Labels: stale-P2
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The new Samza 1.1.0 version introduces a backward incompatible change which
> requires setting both app.id and job.id. We need to make sure setting both in
> SamzaRunner.
> Also add more logs to it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
