[
https://issues.apache.org/jira/browse/BEAM-5396?focusedWorklogId=179536&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-179536
]
ASF GitHub Bot logged work on BEAM-5396:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Dec/18 19:06
Start Date: 28/Dec/18 19:06
Worklog Time Spent: 10m
Work Description: mxm commented on issue #7362: [BEAM-5396] Assign
portable operator uids
URL: https://github.com/apache/beam/pull/7362#issuecomment-450411071
>There is a commit from another PR included here, is that intentional?
Yes, this is based on #7359 (see description) because the test wouldn't
otherwise run.
> Also, we you able to reproduce the restore error?
As you wrote in the JIRA, it depends on the pipeline. We shouldn't see the
restore error anymore because of the uid assigned to all stateful operators.
Before it would depend on the internal operator ids which only works if the
pipeline generation is deterministic. Perhaps you could re-run your pipeline
with this PR to verify that the restore works?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 179536)
Time Spent: 2h 50m (was: 2h 40m)
> Flink portable runner savepoint / upgrade support
> -------------------------------------------------
>
> Key: BEAM-5396
> URL: https://issues.apache.org/jira/browse/BEAM-5396
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Thomas Weise
> Assignee: Maximilian Michels
> Priority: Major
> Labels: portability, portability-flink
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> The portable Flink runner needs to support Flink savepoints for production
> use. It should be possible to upgrade a stateful portable Beam pipeline that
> runs on Flink, which involves taking a savepoint and then starting the new
> version of the pipeline from that savepoint. The potential issues with
> pipeline evolution and migration are similar to those when using the Flink
> DataStream API (schema / name changes etc.).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
