[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640679#comment-14640679
]
Benedict commented on CASSANDRA-6477:
-------------------------------------
The writeOrder is Keyspace-wide, so 2is pass the same writeOrder into their
updates as was used for the outer update, yeah.
Won't comment on the best way to do this with batchlog, given it's a different
keyspace. One possible solution is to make the writeOrder completely global.
There isn't actually anything terrifyingly bad about doing that, although it
would be preferable not to. Another option is to always mark the batchlog
"blocking" whenever you mark another keyspace blocking. There is perhaps
another option that simply separates the two so they aren't so directly
dependent.
> 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)
