[ 
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847022#action_12847022
 ] 

Stu Hood commented on CASSANDRA-749:
------------------------------------

> So in practice I strongly suspect this will scale at least to hundreds of 
> nodes if not thousands
> so saying "we can't do this because it won't scale" is not a strong argument. 
I think you're making the "speed == scalability" mistake. It doesn't matter if 
we could do 30k index queries per second on one node: your bound for index 
queries for the entire cluster would still be 30k, no matter how many nodes you 
added.

> So you have to check each index hit for validity *each* *time* which is a 
> huge hit.
You have to do the same thing for the secondary index: presumably you actually 
want to find the content of the row that was indexed, and so you need to seek 
to the row in the indexed CF. Both solutions need this seek: one just performs 
it across the network.

> you have no way of knowing if that's because another process is about to 
> clean out the index entry, or add the natural entry.
This is a problem: I'll admit. One option is to do something like 
'view-read-repair': when retrieving the indexed row from the base, only clean 
up an invalid index entry after enough time has passed since the entries' 
creation time for any in flight-writes to have completed.

----

I think I'm convinced that fully materialized views will not be able to be 
consistent (even eventually), since the nodes storing the base/view are 
probably in different scopes of serializability. BUT I'm sticking to the idea 
that the partitioned view that queries the base for the row content is the 
superior one.

> Secondary indices for column families
> -------------------------------------
>
>                 Key: CASSANDRA-749
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-749
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: 0001-simple-secondary-indices.patch, 
> views-discussion-2.txt, views-discussion.txt
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to