[
https://issues.apache.org/jira/browse/SAMZA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231694#comment-14231694
]
Chris Riccomini commented on SAMZA-354:
---------------------------------------
Doh, you're right. Missed this. Solutions that I can think of:
# Patch on master. This would mean that users of 0.8.0 would have to look at
the "latest" docs for checkpoint migration tool information.
# Patch on 0.8.0, and have to call another vote (after last one just passed) to
do another source release.
# Create an 0.8.1 branch with this fix in it, and point the docs on the site to
0.8.1 not 0.8.0.
# Manually edit the 0.8.0 files (it's just an SVN checkout) to point to the
tutorial on master.
Personally, I'm OK with (1) or (4), but others might differ. I'm reluctant to
do (2) because the release has already been dragging on for weeks, and I'd like
to just get it out.
> 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)
