[
https://issues.apache.org/jira/browse/COUCHDB-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson closed COUCHDB-76.
---------------------------------
Resolution: Fixed
applied patch from Paul Davis via
http://github.com/davisp/couchdb/tree/reduceonly
> API access to the Map side of Map/Reduce pairs
> ----------------------------------------------
>
> Key: COUCHDB-76
> URL: https://issues.apache.org/jira/browse/COUCHDB-76
> Project: CouchDB
> Issue Type: Wish
> Components: HTTP Interface
> Reporter: Chris Anderson
> Priority: Minor
>
> Everytime I create a reduce function, I also make a separate view that has a
> byte-identical map (w/o the reduce), just to have access to the map that gets
> generated anyway. It seems like the API could make the map side available,
> even when there is a reduce. Keeping the two view functions identical is hard
> to do without automating it, and the consequences of failing to keep them in
> sync can be expensive.
> This would require a change to the external api, because currently the only
> way to distinguish between map and reduce functions is through view name. The
> new way would require something like
> /my-db/_view/mydesign/mymapreduce?map_only=true or somesuch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
