Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-dev@incubator.apache.org
Message-ID: <1525499056.1216372351738.JavaMail.jira@brutus>
Date: Fri, 18 Jul 2008 02:12:31 -0700 (PDT)
From: "Jan Lehnardt (JIRA)" <jira@apache.org>
To: couchdb-dev@incubator.apache.org
Subject: [jira] Resolved: (COUCHDB-15) Error inserting attachment with empty
 data
In-Reply-To: <1997285694.1205020546256.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt resolved COUCHDB-15.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.8.1

Fixed in 677682

> Error inserting attachment with empty data
> ------------------------------------------
>
>                 Key: COUCHDB-15
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-15
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.7.2, 0.8
>            Reporter: Noah Slater
>             Fix For: 0.8.1
>
>
> What steps will reproduce the problem?
> 1. Insert a document like: {"_attachments": {"foo": {"data": ""}}}
> What is the expected output? What do you see instead?
> I'd expect it to add the 0-length attachment, but I get this error in the log:
> [info] [<0.1541.0>] HTTP Error (code 500): {obj,[{error,"EXIT"},
>                              {reason,"{function_clause,[{couch_util,decode1,[undefined]},\n                  
> {couch_util,decodeBase64,1},\n                  {couch_doc,'-from_json_obj/1-fun-0-',1},\n                  
> {lists,flatmap,2},\n                  {couch_doc,from_json_obj,1},\n                  
> {mod_couch,handle_doc_put,2},\n                  {mod_couch,do,1},\n                  
> {httpd_response,traverse_modules,2}]}"}]}
> What version of the product are you using? On what operating system?
> This happens on 0.7.2 and trunk

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.