Repair Tool for CouchDB 1.0.0 bug
wiki.couchone.com
Repair Tool for CouchDB 1.0.0 bug
1–8 of 8 posts
Re: Repair Tool for CouchDB 1.0.0 bug
#2On a side note, they clearly jumped the version number to "1.0" way too soon. It is nowhere near production-worthy software (which is implied by a 1.0 release).
Re: Repair Tool for CouchDB 1.0.0 bug
#3Why is taking so long for 1.0.1 to be released? On a side note, they clearly jumped the version number to "1.0" way too soon. It is nowhere near production-worthy software (which is implied by a 1.0 release).
As far as 1.0 being production ready, yes the bug is unfortunate, but the fix is 29 characters long. Aside from this unfortunate line of code, I'm 100% certain that CouchDB is production ready. Lots of sites have been running it in production for years without issue. An incomplete list of happy users is here: http://www.couch.io/case-studies
Here's the bug-fix, to give you an idea:
http://github.com/apache/couchdb/commit/1423d6f0a593e1681706...
Re: Repair Tool for CouchDB 1.0.0 bug
#4Re: Repair Tool for CouchDB 1.0.0 bug
#5Why is taking so long for 1.0.1 to be released? On a side note, they clearly jumped the version number to "1.0" way too soon. It is nowhere near production-worthy software (which is implied by a 1.0 release).
Re: Repair Tool for CouchDB 1.0.0 bug
#6Even though I like CouchDB, I find their slogan "CouchDB, relax" pretty ironic right now!
"As long as you have not compacted since installing 1.0.0 and triggering the bug, this tool can help you avoid any data loss. Because CouchDB has an append-only file format, the tool is able to recover any data written, even if your server has been restarted since then."
I think it's pretty relaxing imo to know your data are still here.
Re: Repair Tool for CouchDB 1.0.0 bug
#7Why is taking so long for 1.0.1 to be released? On a side note, they clearly jumped the version number to "1.0" way too soon. It is nowhere near production-worthy software (which is implied by a 1.0 release).
Apache procedure requires a 72-hour vote window, which will be closing soon. As far as 1.0 being production ready, yes the bug is unfortunate, but the fix is 29 characters long. Aside from this unfortunate line of code, I'm 100% certain that CouchDB is production ready. Lots of sites have been running it in production for years without issue. An incomplete list of happy users is here: http://www.couch.io/case-studies…