[
https://issues.apache.org/jira/browse/CASSANDRA-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192212#comment-16192212
]
Jeff Jirsa commented on CASSANDRA-13934:
----------------------------------------
I suspect you'll need to demonstrate a clear win in terms of real performance
in order to convince a committer to add this. Part of this is that third party
drivers also need to implement the hash for load balancing policies, so adding
a new partitioner in 4.0 would necessitate a lot of external changes over code
that we don't control. That's not to say it can't be done, but you'll want to
look at some of the testing in CASSANDRA-3772 (for example) to see what was
done previously.
> xxHash as a new partitioner
> ---------------------------
>
> Key: CASSANDRA-13934
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13934
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Salih Gedik
> Priority: Minor
>
> Hi,
> According to [benchmarks|https://cyan4973.github.io/xxHash/] xxHash seems to
> be more performant when used as a consistent hasher. I would like to
> implement xxHash as a partitioner for Cassandra. It should not be strictly
> the default partitioner but as an optional. I am happy to have your ideas
> related to this.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
