cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-510) reading from large supercolumns is excessively slow
Date Wed, 04 Nov 2009 15:51:32 GMT

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

Jonathan Ellis commented on CASSANDRA-510:
------------------------------------------

what's happening is it is being supressed by the

        rm.delete(new QueryPath("Super1", "SC1".getBytes()), 1);

in another test method.

different test classes are run in different jvms w/ the junit fork option (this is the only
sane way to clean out all the stuff that isn't meant to be cleaned out in a running Cassandra),
but methods w/in the same class are not.  so you have to be a little extra careful.

I created a new columnfamily Super3 in the test config and had this test use that, and it
passes as expected now.

I'll commit like that.

> reading from large supercolumns is excessively slow
> ---------------------------------------------------
>
>                 Key: CASSANDRA-510
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-510
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.5
>
>         Attachments: 0001-CASSANDRA-510-don-t-removeDeleted-on-the-whole-CF-befo.txt,
0002-convert-removeDeleted-on-SC-to-remove-oriented-instead.txt
>
>


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


Mime
View raw message