[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849345#action_12849345
]
Jonathan Ellis commented on CASSANDRA-749:
------------------------------------------
> First, they're hosted on Bigtable, so of course they need timeouts. Second,
> they have a section titled "Constraints Precede Performance", which shows why
> you should constrain queries rather than allowing queries that will be slow.
The point is that indexed queries are *still slow* (hundreds of ms) on app
engine.
> This applies to both local and distributed indexes
But with local it's all ... local.
> This was one of the points of that timeout parameter being set higher than a
> write might take to complete: if a write was still in progress (view clock
> doesn't match base clock), we wouldn't populate the view.
This is failing the "complex solutions will bite you" smoke test.
> 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.
