[
https://issues.apache.org/jira/browse/FLINK-26916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514585#comment-17514585
]
Yang Wang commented on FLINK-26916:
-----------------------------------
> As long as the operator has access to user credentials (s3), can you simply
> get the latest checkpoint directly from the filesystem?
I have also considered the solution to scan the DFS checkpoint directory to get
the latest checkpoint. It seems that we do not have a ready-made utility method
for this. I guess it will be a little heavy and we need to force users to
enable external checkpoint. Do I miss something?
> The Operator ignores job related changes (jar, parallelism) during last-state
> upgrades
> --------------------------------------------------------------------------------------
>
> Key: FLINK-26916
> URL: https://issues.apache.org/jira/browse/FLINK-26916
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-0.1.0, kubernetes-operator-1.0.0
> Reporter: Matyas Orhidi
> Assignee: Yang Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-0.1.0
>
>
> RC: The old jobgraph is being reused when resuming
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
