You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2014/12/10 00:02:13 UTC

[jira] [Commented] (KAFKA-1816) Topic configs reset after partition increase

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

Jay Kreps commented on KAFKA-1816:
----------------------------------

I think we fixed this in 0.8.2 though I don't recall the JIRA.

> Topic configs reset after partition increase
> --------------------------------------------
>
>                 Key: KAFKA-1816
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1816
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.1.1
>            Reporter: Andrew Jorgensen
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.8.3
>
>
> If you alter a topic to increase the number of partitions then the configuration erases the existing configs for that topic. This can be reproduces by doing the following:
> {code:none}
> $ bin/kafka-topics.sh --create --zookeeper localhost --topic test_topic --partitions 5 --config retention.ms=3600
> $ bin/kafka-topics.sh --describe --zookeeper localhost --topic test_topic
> > Topic:test_topic        PartitionCount:5        ReplicationFactor:1     Configs:retention.ms=3600
> $ bin/kafka-topics.sh --alter --zookeeper localhost --topic test_topic --partitions 10
> $ bin/kafka-topics.sh --describe --zookeeper localhost --topic test_topic
> > Topic:test_topic        PartitionCount:10        ReplicationFactor:1     Configs:
> {code}



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