couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-415) View sorting
Date Thu, 20 Aug 2009 20:16:14 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745609#action_12745609
] 

Chris Anderson commented on COUCHDB-415:
----------------------------------------

I'm not that into this patch, because it will require complex optimizations to work on view
queries with more than a trivial number of rows. Otherwise we'll asking the Erlang VM to store
the entirety of the view query in memory, and that's not feasible.

Footrest looks like it's coming along, now that it has the ability to use another CouchDB
database as a scratch pad.

I also don't think this blocks the user-definable collations. Those don't suffer from the
same memory usage problems, as they are applied one row at a time when the rows are indexed.

> View sorting
> ------------
>
>                 Key: COUCHDB-415
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-415
>             Project: CouchDB
>          Issue Type: Wish
>    Affects Versions: 0.9
>            Reporter: Nils Breunese
>
> I'd like to be able to sort the output of a view. I have a view that generates a list
of event objects with start and end timestamps (and some other data). I emit this data using
the end timestamp as the key, because that is what I want to use for my ?startkey=... query.
But I'd like the results to be sorted by the start timestamp. I understand this is not currently
possible using regular CouchDB views.
> The CouchDB Users mailinglist suggested to use couchdb-lucene, as that does offer the
option to sort on any indexed field. I'm trying that route now, but it feels like overkill
to add a full-text indexer to CouchDB just to be able to sort the output of my view.
> Some soundbites from the IRC channel when I brought this up:
> ----
> <rnewson> breun: jan___: in this case the data to sort on is known at map time,
so an extension to emit to support multiple keys (with separate btrees) would do it. not sure
how much effort that is, though.
> <rnewson> sorting at query time feels infeasible.
> <jan____> rnewson: I think davisp had something like that working back in the day.
i.e. alternate sort oder. davisp?
> <rnewson> jan___: I missed that, but it sounds reasonable at emit time.
> <davisp> I think its this one: http://github.com/davisp/couchdb-old-patches/tree/view-sort
> ----
> I would love to have view sorting native in CouchDB.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message