couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joan Touzet (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1053) missing_named_view for reduce fxns that compile but throw runtime errors
Date Sat, 26 Jan 2013 20:33:12 GMT


Joan Touzet commented on COUCHDB-1053:

In 1.3.x and master, we no longer throw missing_named_view.

If you have a run-time error in a reduce or map function, the error is logged to the logfile
as, for example:

[info] [<0.638.0>] OS Process #Port<0.3197> Log :: function raised exception (new
TypeError("This is a fake TypeError.", "undefined", 1))

, but we still return a 200 with any results that manage to successfully return. If no results
are returned, it looks like:


for a reduce=true and 



for a reduce=false.

Recommend closing as the error reported by the original poster is no longer accurate. This
is about the best we can do, though in the future we could consider a 5xx upon any thrown
> missing_named_view for reduce fxns that compile but throw runtime errors
> ------------------------------------------------------------------------
>                 Key: COUCHDB-1053
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>         Environment: OSX, prebuilt
>            Reporter: Ryan Richt
>            Assignee: Joan Touzet
>            Priority: Trivial
>             Fix For: 1.3
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Attempting to query a map-only view with reduce=false yields the same error message as
(1) a view that is undefined and (2) a view that has a defined, compile-time valid, but run-time
invalid reduce function. So if your reduce function throws a TypeError, you get this cryptic
error (cryptic b/c so many problems yield the same error) instead of an error to that effect.
Errors do show up in the log, and this is what the view gives:
> {"error":"not_found","reason":"missing_named_view"}
> Might be fixed in 1.0.2 but I cant use the built-in updater anymore after corporate firewall

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message