[
https://issues.apache.org/jira/browse/CASSANDRA-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979567#action_12979567
]
Jonathan Ellis commented on CASSANDRA-1958:
-------------------------------------------
bq. why not to sort after merge iterators?
because we know each input is in sorted order so it's faster to merge
sequentially (this is what CollatedIterator + ReducingIterator do) than to sort
at all.
> query slow in million columns of one key
> ----------------------------------------
>
> Key: CASSANDRA-1958
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1958
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6.5
> Environment: three nodes with SUSE and 2G JVM.
> Reporter: lichenglin
>
> We get all records in 200 ms with 10,000 columns of one key, but 4 seconds
> with 100,000 columns, and we fear for 1,000,000.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
