couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Kitto (Updated) (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-1440) Permanent Erlang views not working on CouchDB 1.1.1
Date Thu, 15 Mar 2012 03:06:19 GMT


Nick Kitto updated COUCHDB-1440:

    Attachment: jira-couch.log

The associated logfile when it is viewed inside Futon
> Permanent Erlang views not working on CouchDB 1.1.1
> ---------------------------------------------------
>                 Key: COUCHDB-1440
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: View Server Support
>    Affects Versions: 1.1.1
>         Environment: Microsoft Windows 7
>            Reporter: Nick Kitto
>              Labels: Bug, Erlang, Error
>         Attachments: jira-couch.log
> Erlang views are fully enabled and work when they are temporary views. When they are
saved into my design document via futon they no longer work.
> An example view that I am trying to use is
> fun ({Doc}) ->
>   case proplists:get_value(<<"doctype">>, Doc) of
>     <<"collections">> ->
>       Emit(proplists:get_value(<<"_id">>, Doc), {Doc});
>     _ ->
>       ok
>   end
> end.
> The copy inside the design document looks like this when it is saved from futon or pushed
using couchapp
> "map": "fun ({Doc}) ->\r\n  case proplists:get_value(<<\"doctype\">>,
Doc) of\r\n    <<\"collections\">> ->\r\n      Emit(proplists:get_value(<<\"_id\">>,
Doc), {Doc});\r\n    _ ->\r\n      ok\r\n  end\r\nend."
> When the view is run directly via the url (ie. localhost:5984/couchapp/_design/jobs/_view/fields)
there is no response inside couch.log and nothing loads.
> When the view is run in futon the error recieved is
> Error: An error occurred accessing the view
> no response
> and it spits out a huge logfile (see attachment)

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


View raw message