[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649520#comment-14649520
]
Ariel Weisberg commented on CASSANDRA-6477:
-------------------------------------------
bq. Recommitted with fix. Looks like those errors are fixed in my test run
above. But we have so many flappy tests it's hard to tell at the moment. Went
from 38 to 22 vs 19 on trunk. Care to double check Ariel Weisberg?
I agree the flappy tests make it really annoying and time consuming. Right now
what I do is for every failing test in the build on my branch is look up the
test history on trunk. If it fails on trunk then I ignore it. That's how I got
to looking into cassci page load times...
This is why I am really bummed about all the regressions in utests and dtests.
It renders the entire CI process either very labor intensive or useless. But
once we work it off and have it clean it's MUCH easier to keep it clean.
I compared them. It did take 10 minutes :-( There are some things that are
passing on trunk due to fixes that came in after the branch was rebased, but
not things that look like regressions.
> 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 alpha 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)
