Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 8 Jan 2013 01:44:12 +0000 (UTC)
From: "Sriram Subramanian (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12618781.1354651442108.94672.1357609452929@arcas>
In-Reply-To: <JIRA.12618781.1354651442108@arcas>
References: <JIRA.12618781.1354651442108@arcas>
Subject: [jira] [Updated] (KAFKA-648) Use uniform convention for naming
 properties keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sriram Subramanian updated KAFKA-648:
-------------------------------------

    Attachment: configchanges-v2.patch

1. Standardized usage of enable
2. Fixed config names in SyncPRoducerConfigShared and AsyncProducerConfig
3. Made the property changes in system_tests, perf
                
> Use uniform convention for naming properties keys 
> --------------------------------------------------
>
>                 Key: KAFKA-648
>                 URL: https://issues.apache.org/jira/browse/KAFKA-648
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8
>            Reporter: Swapnil Ghike
>            Assignee: Sriram Subramanian
>            Priority: Blocker
>             Fix For: 0.8, 0.8.1
>
>         Attachments: configchanges-1.patch, configchanges-v2.patch
>
>
> Currently, the convention that we seem to use to get a property value in *Config is as follows:
> val configVal = property.getType("config.val", ...) // dot is used to separate two words in the key and the first letter of second word is capitalized in configVal.
> We should use similar convention for groupId, consumerId, clientId, correlationId.
> This change will probably be backward non-compatible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira