[
https://issues.apache.org/jira/browse/CASSANDRA-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194426#comment-14194426
]
Branimir Lambov commented on CASSANDRA-8143:
--------------------------------------------
This is turning into a very substantial refactor. The assumption that there is
only one partitioner runs very deeply through the code, and some core
functionality (e.g. ranges) appears broken in subtle ways when this is not the
case.
I think it is well worth removing as many hidden references to the database
partitioner as possible and clarifying where the partitioner used comes from.
This turns out to be a substantial change, and I'm going to split it into
several smaller steps as one single big change will be too difficult to review
(and justify).
> 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)
