You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Martin Kleppmann (JIRA)" <ji...@apache.org> on 2014/12/02 08:46:13 UTC

[jira] [Commented] (SAMZA-354) Write tool to convert old-style checkpoint log to post-SAMZA-123 format

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

Martin Kleppmann commented on SAMZA-354:
----------------------------------------

Do we have any docs for CheckpointMigrationTool? It would be good to have a description of how to use this tool on the website before we announce the 0.8.0 release. The [tutorials section|http://samza.incubator.apache.org/learn/tutorials/latest/] would probably be a good place.

> Write tool to convert old-style checkpoint log to post-SAMZA-123 format
> -----------------------------------------------------------------------
>
>                 Key: SAMZA-354
>                 URL: https://issues.apache.org/jira/browse/SAMZA-354
>             Project: Samza
>          Issue Type: Task
>    Affects Versions: 0.8.0
>            Reporter: Jakob Homan
>            Assignee: Navina Ramesh
>             Fix For: 0.8.0
>
>         Attachments: SAMZA-354-CheckpointMigrationTool-ver-1.patch, SAMZA-354-CheckpointMigrationTool.patch
>
>
> After SAMZA-123, the checkpoint log has a new format (keyed entries interspersed with statelog-partition mapping) and a new name.  It would be simple to write a tool that would consume an old-style log and write out a new-style log, using the GroupByPartition strategy.  This would allow existing jobs to not lose checkpointing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)