[ https://issues.apache.org/jira/browse/CASSANDRA-14798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664309#comment-16664309 ]
Dinesh Joshi commented on CASSANDRA-14798: ------------------------------------------ LGTM > Improve wording around partitioner selection > -------------------------------------------- > > Key: CASSANDRA-14798 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14798 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website > Reporter: Aaron Ploetz > Assignee: Aaron Ploetz > Priority: Trivial > Fix For: 4.0 > > Attachments: 14798-trunk.patch > > > Given some recent community interactions on Stack Overflow, Nate McCall asked > me provide some stronger wording on partitioner selection. Specifically, in > further discouraging people from using the other partitioners (namely, the > ByteOrderedPartitioner). > Right now, this is the language that I'm leaning toward: > {{# The partitioner is responsible for distributing groups of rows (by}} > {{# partition key) across nodes in the cluster. The partitioner can NOT be}} > {{# changed without reloading all data. If you are upgrading, you should set > this}} > {{# to the same partitioner that you are currently using.}} > {{#}} > {{# The default partitioner is the Murmur3Partitioner. Older partitioners}} > {{# such as the RandomPartitioner, ByteOrderedPartitioner, and}} > {{# OrderPreservingPartitioner have been included for backward compatibility > only.}} > {{# For new clusters, you should NOT change this value.}} > {{#}} > {{partitioner: org.apache.cassandra.dht.Murmur3Partitioner }} > I'm open to suggested improvements. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org