[
https://issues.apache.org/jira/browse/FLINK-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029625#comment-17029625
]
Bastien DINE edited comment on FLINK-15863 at 2/4/20 7:58 AM:
--------------------------------------------------------------
Hello [~NicoK],
Maybe we can just simplify it, by just removing the reference of 1.3
Savepoints, with modification by State Processor API, can also reference other
savepoints (as do incremental checkpoiting with checkpoint)
And this is absolute path, so this is non relocatable too
Maybe something like :
{code:java}
Another important precondition is that all the savepoint data must be
accessible from the new installation. Additional files can be referenced from
inside the savepoint file (e.g. the output from state backend snapshots) and
savepoint can referenced others (e.g. modification with State Processor API
*link* ?) The savepoint data are referenced through absolute path by meta data
file and thus, the savepoint is typically not relocatable using typical
filesystem operations.
{code}
was (Author: bdine):
Hello [~NicoK],
Maybe we can just simplify it, by just removing the reference of 1.3
Savepoints, with modification by State Processor API, can also reference other
savepoints (as do incremental checkpoiting with checkpoint)
And this is absolute path, so this is non relocatable too
Maybe something like :
{code:java}
Another important precondition is that all the savepoint data must be
accessible from the new installation and reside under the same absolute path.
Additional files can be referenced from inside the savepoint file (e.g. the
output from state backend snapshots) and savepoint can referenced others (e.g.
modification with State Processor API *link* ?) The savepoint data are
referenced through absolute path by meta data file and thus, the savepoint is
typically not relocatable using typical filesystem operations.
{code}
> Fix docs stating that savepoints are relocatable
> ------------------------------------------------
>
> Key: FLINK-15863
> URL: https://issues.apache.org/jira/browse/FLINK-15863
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 1.9.2, 1.10.0
> Reporter: Nico Kruber
> Priority: Blocker
> Labels: usability
> Fix For: 1.11.0, 1.10.1
>
>
> This section from
> https://ci.apache.org/projects/flink/flink-docs-stable/ops/upgrading.html#preconditions
> states that savepoints are relocatable which they are not yet (see
> FLINK-5763). It should be fixed and/or removed; I'm unsure what change from
> 1.3 it should actually reflect.
> {quote}Another important precondition is that for savepoints taken before
> Flink 1.3.x, all the savepoint data must be accessible from the new
> installation and reside under the same absolute path. Before Flink 1.3.x, the
> savepoint data is typically not self-contained in just the created savepoint
> file. Additional files can be referenced from inside the savepoint file (e.g.
> the output from state backend snapshots). Since Flink 1.3.x, this is no
> longer a limitation; savepoints can be relocated using typical filesystem
> operations..{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
