You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
I'm new to bigcouch. I decided to port my Couchdb 1.2 databases to BigCouch 0.4 (on Linux EC2). I made the required changes to comply with the BG API. I encounter a problem when I use attachments. I can upload a file (image1.jpg) with no issue but then I can't update the document having the attachment. I always get a HTTP 412 {"error":"missing_stub","reason":"Invalid attachment stub in 83327ed26d618a6981b81cc2b901f78b for image1.jpg"}. The image is OK, I can see it in Futon.
After a couple of hours of testing, I realized the issue is related to my design document written in erlang. If I remove the validate_doc_update function, it fixes the issue. But the way, the erlang views works fine. I wrote the validate_doc_update function in a different design doc written in javascript to workaround.
I hope it can help others if they get the same kind of issue until a patch is made.
Jeff
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I'm new to bigcouch. I decided to port my
Couchdb 1.2
databases toBigCouch 0.4
(on Linux EC2). I made the required changes to comply with the BG API. I encounter a problem when I use attachments. I can upload a file (image1.jpg) with no issue but then I can't update the document having the attachment. I always get a HTTP 412 {"error":"missing_stub","reason":"Invalid attachment stub in 83327ed26d618a6981b81cc2b901f78b for image1.jpg"}. The image is OK, I can see it in Futon.After a couple of hours of testing, I realized the issue is related to my design document written in erlang. If I remove the validate_doc_update function, it fixes the issue. But the way, the erlang views works fine. I wrote the validate_doc_update function in a different design doc written in javascript to workaround.
I hope it can help others if they get the same kind of issue until a patch is made.
Jeff
The text was updated successfully, but these errors were encountered: