[jira] [Commented] (SAMZA-689) When Kafka has topic auto-creation turned on, checkpoint and changelog topics may be created w/ wrong partition numbers

["Yan Fang (JIRA)" <ji...@apache.org>]

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

Yan Fang commented on SAMZA-689:
--------------------------------

1. Isn't the checkpoint topic embedded into the CoordinatorStream and there is not separate checkpoint topic?

2. For the changelog, I think we are doing this way, in the KafkaAdmin [createChangelogStream|https://github.com/apache/samza/blob/master/samza-kafka/src/main/scala/org/apache/samza/system/kafka/KafkaSystemAdmin.scala#L395]

Wondering it's really an issue.

> When Kafka has topic auto-creation turned on, checkpoint and changelog topics may be created w/ wrong partition numbers
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-689
>                 URL: https://issues.apache.org/jira/browse/SAMZA-689
>             Project: Samza
>          Issue Type: Bug
>          Components: container
>    Affects Versions: 0.9.1
>            Reporter: Yi Pan (Data Infrastructure)
>            Assignee: Navina Ramesh
>             Fix For: 0.9.1
>
>
> When Kafka topic auto-creation is turned on in the brokers, a fetch metadata API call will result in topic auto-creation w/ default number of partitions.
> In Samza code, we should always try to create the checkpoint/changelog topic w/ the expected number of partitions first, then call fetch metadata to avoid topic auto-creation creating the topic w/ un-wanted number of partitions.



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