[
https://issues.apache.org/jira/browse/CASSANDRA-10489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950117#comment-14950117
]
Sylvain Lebresne commented on CASSANDRA-10489:
----------------------------------------------
For the "non-indexed" part, the big problem with this is paging. I don't think
we can do arbitrary read-time ordering in the presence of paging, at least not
given how things work. And I'm *very* opposed to supporting it only if the user
disable paging as 1) that would be really confusing, 2) that would be
encouraging users to disable paging which we don't want and 3) sorting client
side ain't that hard. And at least in that "non-indexed" case, I don't buy the
"it's better to do it server side if you want a LIMIT" argument: pulling 10k
rows in memory to sort them when you only care about the 10 first one is a
stupid idea whether that's client or server side, you should use a MV (or any
other smarter solution).
As for the "indexed" part, I kind of think that it's what MVs are for. Of
course, if you see a much better way to do this that through MVs, feel free to
share.
> 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)
