[
https://issues.apache.org/jira/browse/CASSANDRA-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388678#comment-14388678
]
Bryn Cooke commented on CASSANDRA-8143:
---------------------------------------
If the partitioner could be defined at the column family level then the
location of data can be tuned to the dataset. Combined with custom secondary
index implementations this could be a very powerful feature as you could
effectively tune data locality and do local reads where appropriate.
Support would need to be all the way up to the CQL level though.
> Partitioner should not be accessed through StorageService
> ---------------------------------------------------------
>
> Key: CASSANDRA-8143
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8143
> Project: Cassandra
> Issue Type: Bug
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Minor
> Fix For: 3.0
>
>
> The configured partitioner is no longer the only partitioner in use in the
> database, as e.g. index tables use LocalPartitioner.
> To make sure the correct partitioner is used for each table, accesses of
> StorageService.getPartitioner() should be replaced with retrieval of the
> CFS-specific partitioner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
