[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635374#comment-14635374
]
Joshua McKenzie commented on CASSANDRA-6477:
--------------------------------------------
h6. 0d77f03: lgtm
h6. 2707065
* Should we formalize the "MV threads should be == less of readers or writers"
in the configuration code and warn if it's set incorrectly?
* Do we have any data around the # of batchlog writing threads as to why 32 is
a good #?
h6. 8eaa95e: lgtm
h6. b4d3d99:
* In MaterializedViewTest, can have updateMV not return anything since nobody's
using return which makes the driver ResultSet inclusion unnecessary.
> Materialized Views (was: Global Indexes)
> ----------------------------------------
>
> Key: CASSANDRA-6477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0 beta 1
>
> Attachments: test-view-data.sh, users.yaml
>
>
> Local indexes are suitable for low-cardinality data, where spreading the
> index across the cluster is a Good Thing. However, for high-cardinality
> data, local indexes require querying most nodes in the cluster even if only a
> handful of rows is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
