You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Gary Dusbabek (JIRA)" <ji...@apache.org> on 2009/11/03 23:00:32 UTC
[jira] Commented: (CASSANDRA-510) reading from large supercolumns
is excessively slow
[ https://issues.apache.org/jira/browse/CASSANDRA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773232#action_12773232 ]
Gary Dusbabek commented on CASSANDRA-510:
-----------------------------------------
Just a few noob questions...
Would it be useful to include a test that verifies that an unintended sub column is *not* removed?
Why does cloneMe() call markForDeleteAt?
> 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.