cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Shook (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10489) arbitrary order by on partitions
Date Thu, 08 Oct 2015 23:41:27 GMT

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

Jonathan Shook commented on CASSANDRA-10489:
--------------------------------------------

I'm totally cool with a threshold warning here. But something that is easily ignored is easily
ignored, like log spam. Also, if it is documented clearly in terms of op costs, I'm ok with
that too. Anywhere we have a list of "these things that can be expensive if you don't understand
what they are doing", this should be on it.

> arbitrary order by on partitions
> --------------------------------
>
>                 Key: CASSANDRA-10489
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10489
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jon Haddad
>            Priority: Minor
>
> We've got aggregations, we might as well allow sorting rows within a partition on arbitrary
fields.  Currently the advice is "do it client side", but when combined with a LIMIT clause
it makes sense do this server side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message