Question

This is on a recent version of couchbase server.

The end goal is for the reduce/groupby to aggregate the values of the duplicate keys in to a single row with an array value.

view result with no reduce/grouping (in reality there are maybe 50 rows like this emitted):

{
"total_rows": 3,
"offset": 0,
"rows": [
{
"id": "1806a62a75b82aa6071a8a7a95d1741d",
"key": "064b6b4b-8e08-4806-b095-9e59495ac050",
"value": "1806a62a75b82aa6071a8a7a95d1741d"
},
{
"id": "47abb54bf31d39946117f6bfd1b088af",
"key": "064b6b4b-8e08-4806-b095-9e59495ac050",
"value": "47abb54bf31d39946117f6bfd1b088af"
},
{
"id": "ed6a3dd3-27f9-4845-ac21-f8a5767ae90f",
"key": "064b6b4b-8e08-4806-b095-9e59495ac050",
"value": "ed6a3dd3-27f9-4845-ac21-f8a5767ae90f"
}
}

with reduce + group_level=1:

function(keys,values,re){
  return values;
}

yields an error from couch with the actual 50 or so rows from the real view (even fails with fewer view rows). couch says something about the data not shrinking rapidly enough. However this same type of thing works JUST FINE when the view keys are integers and there is a small amount of data.

Can someone please explain the difference to me?

Answer 1

I am almost always going to be querying this view with a “key” parameter, so there really is no need to aggregate values via couch, it can be easily and efficiently done in the app.