[jira] [Commented] (SAMZA-330) Checkpoint log and state log should resize partition count upward if necessary at job start

["Chris Riccomini (JIRA)" <ji...@apache.org>]

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

Chris Riccomini commented on SAMZA-330:
---------------------------------------

With SAMZA-71/SAMZA-123, doesn't the checkpoint topic always have 1 partition (partition 0)? Seems like we only need to do this for the changelog topic.

> Checkpoint log and state log should resize partition count upward if necessary at job start
> -------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-330
>                 URL: https://issues.apache.org/jira/browse/SAMZA-330
>             Project: Samza
>          Issue Type: Improvement
>          Components: container, kv
>    Affects Versions: 0.7.0
>            Reporter: Jakob Homan
>
> Currently if a the checkpoint log or state log partition count increases on job restart due to the inclusion of new streams with a higher partition count, the corresponding Kafka topics are increased to accommodate this change.  In the case of the the checkpoint log, we will get a job failure at startup.  We should compare the current partition size with the required and size upward if necessary at job start.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)