[
https://issues.apache.org/jira/browse/COUCHDB-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766267#action_12766267
]
Paul Joseph Davis commented on COUCHDB-530:
-------------------------------------------
I don't think it was an error in 0.9.1 and its possible to disable that check
in the config.
One thing that we have said before is the ability to make views return errors
and warnings to the user from view building but the current setup makes that
somewhat difficult currently.
Also, that error is a bit wonky with the list vs binary confusion. I'll put it
on the list to fix.
> reduce_overflow_error on a view without reduce
> ----------------------------------------------
>
> Key: COUCHDB-530
> URL: https://issues.apache.org/jira/browse/COUCHDB-530
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 0.10
> Environment: Ubuntu 9.04
> Reporter: Miki Tebeka
> Assignee: Paul Joseph Davis
> Attachments: stats.view
>
>
> This view used to work on 0.9.1, I've installed 0.10.0 and migrated some data.
> When running the view I get the following error:
> (env2.5)[11:47] admin $curl
> 'localhost:5985/stats/_design/stats/_view/active'
> {"error":"reduce_overflow_error","reason":"Reduce output must shrink more
> rapidly: Current output:
> '[[25,17,117,25,93,17,13,13,12,24,14,13,10,15,20,12,14,14,17,36,38,83,18,11,1058,12,10,29,13,12,10,14'...
> (first 100 of 1395 bytes)"}
> What's interesting is that this view does not have a reduce function. The map
> function is:
> function (doc) {
> if (doc.Type == 'max active') {
> emit(doc.Time, doc.Count);
> }
> }
> A typical document looks like:
>
> {"_id":"02c94bea2900686a01ebbf8829aabfa2","_rev":"1-cccb3b5eb382bf609bd41feb85af063b","Count":2,"Type":"max
> active","Time":1254362400.0}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
