You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2015/01/20 16:31:35 UTC

[jira] [Resolved] (KAFKA-1337) Rationalize new producer configs

     [ https://issues.apache.org/jira/browse/KAFKA-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao resolved KAFKA-1337.
----------------------------
       Resolution: Fixed
    Fix Version/s: 0.8.2

The followup patch has been committed to 0.8.2. Resolving the jira.

> Rationalize new producer configs
> --------------------------------
>
>                 Key: KAFKA-1337
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1337
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: producer 
>    Affects Versions: 0.8.2
>            Reporter: Jay Kreps
>            Assignee: Jay Kreps
>             Fix For: 0.8.2
>
>         Attachments: KAFKA-1337.patch, KAFKA-1337.patch, KAFKA-1337.patch, KAFKA-1337.patch
>
>
> New producer configs have been added somewhat haphazardly. Before we consider the producer final, let's do the following:
> 1. Go back and think about all the config names and make sure they are really what we want.
> 2. Add doc strings for all the configs
> 3. Make the config keys non-public.
> 4. Add a feature to differentiate important from non-important configs.
> 5. Add code to generate the website documentation off the internal config docs.



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