You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (JIRA)" <ji...@apache.org> on 2011/04/17 15:02:05 UTC

[jira] [Resolved] (COUCHDB-877) Allow a view to use other views internally

     [ https://issues.apache.org/jira/browse/COUCHDB-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt resolved COUCHDB-877.
----------------------------------

    Resolution: Invalid

Stalled ticket, no patch, no comments, closing :) Feel free to reopen when there's new discussion points.

> Allow a view to use other views internally
> ------------------------------------------
>
>                 Key: COUCHDB-877
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-877
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: JavaScript View Server
>    Affects Versions: 1.0.1
>            Reporter: Adriaan vk
>
> It is great that couchdb can store any document on which you can query. After storing tons of documents, it is a common task to 'play' around with the data by filtering on any document-item.
> For playing around, you can use temp views rather then creating every possible filtering view. But since temp views perform bad in a big storage, those needs to be speeded up:
> - Allow a temp view to be created on top of other views. This even allows complex search queries like '> x' or 'contains y', since the set to page through is quite small. Even any kind of sorting can be done using temp views.
> - For this you need also an execution plan for which view you can use best for a first filtering
> - Optimize a temp view when i add things like limit. If i send a tempview to the server with limit 10, currently all docs are processed, while this is not needed.
> - Temp views will also speed up the database, since otherwise we have to persist all possible views, which needs to be updated by each insert. (The same issue as you have in regular databases where you are not creating tons of indexes because of performance)
> If this can be realized, this would improve the usability of couchdb hugh! You can create complex (sub)filtering and sorting on hugh document stores. You also can create (temp)views on user request, speeding up the whole process. This even is required for me to be able to use this great document storage tool.
> Any suggestions are welcome!

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira