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

Joe Stein commented on KAFKA-1761:
----------------------------------

[~sslavic] There are a handful of cases (e.g. 
https://github.com/apache/kafka/blob/0.8.1/core/src/main/scala/kafka/server/KafkaConfig.scala#L69
 which match docs but are overridden to 9092 in property (and we should keep as 
9092 since that is what everyone uses now imho)) of this where the properties 
files are changing what the actual default in the code (when no property is 
set) has. Here the default partition is actually 1 (like the docs say) 
https://github.com/apache/kafka/blob/0.8.1/core/src/main/scala/kafka/server/KafkaConfig.scala#L98
 but the property file has it set it to 2 and we document 1 (because that is 
what the code is). I think all 3 should be consistent and we should try to 
clean this up in all cases (maybe use this ticket to-do so?). If we want 2 to 
be the default then lets change it in the code (though I think 1 as the default 
for setting might ease some FAQ related questions) and use the property file as 
what we think/feel people should be changing during normal operations matching 
1:1 with the code defaults.

> num.partitions        documented default is 1 while actual default is 2
> -----------------------------------------------------------------
>
>                 Key: KAFKA-1761
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1761
>             Project: Kafka
>          Issue Type: Bug
>          Components: log
>    Affects Versions: 0.8.1.1
>            Reporter: Stevo Slavic
>            Assignee: Jay Kreps
>            Priority: Minor
>
> Default {{num.partitions}} documented in 
> http://kafka.apache.org/08/configuration.html is 1, while server 
> configuration defaults same parameter to 2 (see 
> https://github.com/apache/kafka/blob/0.8.1/config/server.properties#L63 )
> Please have this inconsistency fixed.



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

Reply via email to