Alexander Shorin created COUCHDB-2611:
-----------------------------------------
Summary: Integrate mango with mrview
Key: COUCHDB-2611
URL: https://issues.apache.org/jira/browse/COUCHDB-2611
Project: CouchDB
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Mango, View Server Support
Reporter: Alexander Shorin
Mango provides the following HTTP API endpoints: _index, _find and _explain.
The _index is used to create a new views and ddocs, if it wasn't specified in
POST request, and retrieve all the indexed on GET. Pretty nice shortcut to not
deal with all these _design/foo/_views/bar long urls.
But it only works for "json" query language and it's duplicates our current
design document API. So here comes the first issue: you likes mango, you
addicts yourself with _index API, but when you need to operate with good old
javascript ones you have to use different API. Why?
Same happens with index management: mango uses own API, all the views have to
use mrview one. Why?
So actually, you cannot relay on some one API for all kind of views. In general
case you have to avoid mango HTTP API , unless all what you need in mango
queries.
The _find is a brand new temporary views, but again only for mango queries. Why
not to reuse existed API for the same functionality?
Too many questions, no much oblivious answers for such pretty simple questions.
Currently mango looks as an alien addition which users have to avoid. We
shouldn't provide many different ways to do the same things.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
