[jira] [Comment Edited] (KAFKA-2176) DefaultPartitioner doesn't perform consistent hashing based on

["Gwen Shapira (JIRA)" <ji...@apache.org>]

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

Gwen Shapira edited comment on KAFKA-2176 at 5/12/15 6:11 AM:
--------------------------------------------------------------

Do we want to fix this?
It is not an issue in the new Producer, which MirrorMaker can use.

I'm somewhat against continuing to maintain the old clients.


was (Author: gwenshap):
Do we want to fix this?
It is not an issue in the new Producer, which MirrorMaker can use.

> DefaultPartitioner doesn't perform consistent hashing based on 
> ---------------------------------------------------------------
>
>                 Key: KAFKA-2176
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2176
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.1
>            Reporter: Igor Maravić
>              Labels: easyfix, newbie
>             Fix For: 0.8.1
>
>         Attachments: KAFKA-2176.patch
>
>
> While deploying MirrorMakers in production, we configured it to use kafka.producer.DefaultPartitioner. By doing this and since we had the same amount partitions for the topic in local and aggregation cluster, we expect that the messages will be partitioned the same way.
> This wasn't the case. Messages were properly partitioned with DefaultPartitioner on our local cluster, since the key was of the type String.
> On the MirrorMaker side, the messages were not properly partitioned.
> Problem is that the Array[Byte] doesn't implement hashCode function, since it is mutable collection.
> Fix is to calculate the deep hash code if the key is of Array type.



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