[
https://issues.apache.org/jira/browse/CASSANDRA-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649733#comment-14649733
]
Aleksey Yeschenko commented on CASSANDRA-8143:
----------------------------------------------
My apologies for not checking with dtests. Schema propagation was failing,
ultimately because of a bug in {{Mutation.deserialize()}} for size > 1. It
wasn't being caught by any utests (which I had run).
Fix
[here|https://github.com/iamaleksey/cassandra/commit/7aaf15ebd4807b107cf24f47529424102b7ac026],
will revert and commit once
[dtest|http://cassci.datastax.com/view/Dev/view/iamaleksey/job/iamaleksey-8143-dtest/]
and
[testall|http://cassci.datastax.com/view/Dev/view/iamaleksey/job/iamaleksey-8143-testall/]
are both clear.
> Partitioner should not be accessed through StorageService
> ---------------------------------------------------------
>
> Key: CASSANDRA-8143
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8143
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Fix For: 3.0 beta 1
>
>
> 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)
