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/01 18:25:49 UTC

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

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

Guozhang Wang commented on KAFKA-967:
-------------------------------------

Jun, before this patch each message will use a different key in ProducerPerformance, so are you suggesting that if messageKeyRangeOpt it not specified we should still use a distinct key for each message?

Currently if messageKeyRangeOpt is not set it uses a default key range.
                
> 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
>
>
> 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