[
https://issues.apache.org/jira/browse/SAMZA-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120072#comment-14120072
]
Jakob Homan commented on SAMZA-354:
-----------------------------------
bq. If you just expect the devs to do it themselves, then either way should
work. If you expect ops guys to do it, then having the continual loader run
seems preferable, since it requires less coordination.
Either would work. For the devs, it would be an at-their-convenience type of
thing and for the ops team, it could be part of regular scheduled
downtime/maintenance for all the jobs. My guess would be that there's only one
large shop running Samza jobs gated by the ops team. The ops-driven type would
be easily scriptable.
> 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: David Chen
>
> 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)
