Anyone seen this before?
=ERROR REPORT 21-May-2009::16:51:57 ===
Error in process 0.15765.3 with exit value: {{badmatch,undefined},
[{couch_rep,get_missing_revs,2},{couch_rep,enum_docs_since,4}]}
[info] [0.15762.3] 127.0.0.1 - - 'POST' /acumen-content/
_missing_revs 404
[error] [0.275.0]
Ungraceful behaviour if view returns a function
---
Key: COUCHDB-354
URL: https://issues.apache.org/jira/browse/COUCHDB-354
Project: CouchDB
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/COUCHDB-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Candler updated COUCHDB-354:
--
Attachment: test_reduce_barf.rb
Example where re-reduce function accidentally returns a
[
https://issues.apache.org/jira/browse/COUCHDB-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Candler updated COUCHDB-354:
--
Attachment: barf.log
The resulting barf
Ungraceful behaviour if view returns a function
OK, this was stupid stupid user error, but interesting in that I
couldn't stop the replication process - I had to go through the
process list and kill each couchdb process.
This occurs if you pull replicate into a db that hasn't been created.
I think the replicate call should fail in that
Hello,
In 0.9 CouchDB removed the transactional bulk docs feature in favour
of simplifying sharding/replication.
The priorities behind this decision as I understood them are:
1. ensure that applications developed in a single server don't
suffer from a degradation of guarantees if deployed
The reason you can't stop the replication process is because that pid
is supervised and will be restarted in the event of abnormal
termination, even if the HTTP request is canceled.
I agree that it's pretty pointless to keep trying to restart the
replication if the source or target DB does
deleting a _config key sets the value to
---
Key: COUCHDB-355
URL: https://issues.apache.org/jira/browse/COUCHDB-355
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects
1) Generate foo/1 and bar/1 in an atomic _bulk_docs operation
2) Update foo - foo/2
Compact the DB (foo/1 is deleted)
Start replicating to a mirror
Replication crashes before it reaches foo/2
By crash you mean an error due to a conflict between foo/2 and foo/1'
(the mirror's version of
