[
https://issues.apache.org/jira/browse/SAMZA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Navina Ramesh updated SAMZA-354:
--------------------------------
Attachment: SAMZA-354-CheckpointMigrationTool.patch
CheckpointMigrationTool converts 0.7 checkpoint log to 0.8 checkpoint log
format (keyed checkpoint entries)
Differences:
* kafka checkpoint topic name is different from 0.7 checkpoint topic name
* kafka checkpoint topic contains only 1 partition and checkpoint entries are
keyed by SSP (SAMZA-123 for more details)
The tool creates 0.8 checkpoint topic if it doesn't already exist and converts
log entries from 0.7 to 0.8 format. If 0.8 checkpoint topic already exists, it
prompts for user confirmation to proceed with the migration.
> 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.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)
