You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2013/08/05 18:36:48 UTC

[jira] [Updated] (KAFKA-967) Use key range in ProducerPerformance

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

Guozhang Wang updated KAFKA-967:
--------------------------------

    Attachment: KAFKA-967.v3.patch

Now if messageKeyRangeOpt is not specified, null will be passed as the key, and the debug log trace will show 0 as key; if messageKeyRangeOpt is specified, keys will range from 1 to the specified number instead of 0 to the specified number - 1. 
                
> Use key range in ProducerPerformance
> ------------------------------------
>
>                 Key: KAFKA-967
>                 URL: https://issues.apache.org/jira/browse/KAFKA-967
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>         Attachments: KAFKA-967.v1.patch, KAFKA-967.v2.patch, KAFKA-967.v3.patch
>
>
> Currently in ProducerPerformance, the key of the message is set to MessageID. It would better to set it to a specific key within a key range (Integer type) so that we can test the semantic partitioning case. This is related to KAFKA-957.

--
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