cassandra-commits mailing list archives

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

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

Jon Haddad commented on CASSANDRA-10489:
----------------------------------------

I don't see this as any different than selecting 10K rows out of a relational DB and sorting
on one of the fields.  I realize this could potentially be a little ridiculous if you're working
on some crazy time series - at that point you'd want to have multiple tables to manage the
query performance.  There's plenty of cases, however which are limited to hundreds or thousands
of rows which would work perfectly fine with in memory sorting.  An example would be a table
which is hourly aggregated data & you need to find the top 10 hours (of some field, maybe
it's pageviews) in a year.  Really not necessary to have a secondary table for this, and silly
to pull back 8K rows just to sort client side and get the top 10.  

> 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