[ 
https://issues.apache.org/jira/browse/FLINK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031171#comment-16031171
 ] 

ASF GitHub Bot commented on FLINK-6782:
---------------------------------------

Github user alpinegizmo commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4024#discussion_r119358154
  
    --- Diff: docs/setup/savepoints.md ---
    @@ -129,11 +144,11 @@ $ bin/flink savepoint -d :savepointPath
     
     This disposes the savepoint stored in `:savepointPath`.
     
    -Note that since savepoints always go to a file system it is possible to 
also manually delete the savepoint via a regular file system operation. Keep in 
mind though that the savepoint only stores meta data that points to the actual 
checkpoint data. Therefore, if you manually want to delete a savepoint, you 
would have to include the checkpoint files as well. Since there is currently no 
straight forward way to figure out how a savepoint maps to a checkpoint, it is 
recommended to use the savepoint tool for this as described above.
    +Note that since savepoints always go to a file system it is possible to 
also manually delete the savepoint via a regular file system operation. Up to 
Flink 1.2, this way a more tedious task which was solved with this tool.
    --- End diff --
    
    Up to Flink 1.2, this was a more tedious task which was performed with the 
savepoint tool.


> Update savepoint documentation
> ------------------------------
>
>                 Key: FLINK-6782
>                 URL: https://issues.apache.org/jira/browse/FLINK-6782
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Documentation, State Backends, Checkpointing
>    Affects Versions: 1.3.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>             Fix For: 1.3.0
>
>
> Savepoint documentation is a bit outdated regarding full data being stored in 
> the savepoint path, not just a metadata file



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to