[
https://issues.apache.org/jira/browse/BEAM-11748?focusedWorklogId=558762&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-558762
]
ASF GitHub Bot logged work on BEAM-11748:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Feb/21 21:39
Start Date: 26/Feb/21 21:39
Worklog Time Spent: 10m
Work Description: Zhangyx39 commented on pull request #14105:
URL: https://github.com/apache/beam/pull/14105#issuecomment-786908089
@xinyuiscool please help review this pr. Thanks!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 558762)
Time Spent: 20m (was: 10m)
> Fix PViewToIdMapper in Samza runner to not include hashcode as part of the id
> -----------------------------------------------------------------------------
>
> Key: BEAM-11748
> URL: https://issues.apache.org/jira/browse/BEAM-11748
> Project: Beam
> Issue Type: Bug
> Components: runner-samza
> Reporter: Yixing Zhang
> Assignee: Yixing Zhang
> Priority: P2
> Time Spent: 20m
> Remaining Estimate: 0h
>
> PValueBase.toString() now appends the hashcode to the end. This causes the
> PViewToIdMapper generates IDs with hashcode, which can be inconsistent in
> different Samza containers. And therefore causes runtime issues.
> We should exclude the hashcode from the id.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
