[ https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira updated KAFKA-2702: -------------------------------- Resolution: Fixed Fix Version/s: 0.9.0.0 Status: Resolved (was: Patch Available) Issue resolved by pull request 379 [https://github.com/apache/kafka/pull/379] > ConfigDef toHtmlTable() sorts in a way that is a bit confusing > -------------------------------------------------------------- > > Key: KAFKA-2702 > URL: https://issues.apache.org/jira/browse/KAFKA-2702 > Project: Kafka > Issue Type: Bug > Reporter: Gwen Shapira > Assignee: Grant Henke > Fix For: 0.9.0.0 > > Attachments: ConsumerConfig-After-v2.html, ConsumerConfig-After.html, > ConsumerConfig-Before.html > > > Because we put everything without default first (without prioritizing), > critical parameters get placed below low priority ones when they both have > no defaults. Some parameters are without default and optional (SASL server in > ConsumerConfig for instance). > Try printing ConsumerConfig parameters and see the mandatory group.id show up > as #15. > I suggest sorting the no-default parameters by priority as well, or perhaps > adding a "REQUIRED" category that gets printed first no matter what. -- This message was sent by Atlassian JIRA (v6.3.4#6332)