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 21:33:26 GMT

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

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

Would this need to be limited to indexed (in some form) fields? Without an index, it would
be difficult for the coordinator to know the bound of sorting ahead of time. Or would this
be for rows selected by some indexed field with limit, and then sorted only after limit was
applied?

Essentially, should we define this as a valid goal for results for which we already can know
the cardinality bounds without traversing the whole partition?

> 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