Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CouchDB Notice for 1.0.1 - Potential Data Loss

couchdb.apache.org

Post reply on HN
Print view View original

11–20 of 33 posts

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#11

Post by i386 »

StavrosK wrote: post #7
freetard wrote: post #6

Earlier quoted context omitted.

Yes, it was true that the 32bit version of mongodb that is limited to 2gb would lose your data if you injected more than 2gb in it, shame on mongodb...

Jesus, I can't believe people still defend this shit. I don't care if MongoDB can store ten jiggerbytes, it should give an error when you're trying to insert more than that . When the hell did corrupting your data become acceptable for a datastore?

Simple guide to keep your integrity in the software business: don't crap on other peoples products and admit your own mistakes.

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#12

Post by InclinedPlane »

freetard wrote: post #10
StavrosK wrote: post #9

Earlier quoted context omitted.

When did I complain it couldn't store more than 2 GB? I complained because it silently corrupted my data.

You used a dev version of a tool that is not meant to be ran in production or for any serious task and then complained it didn't work with your attempt. As this bug is not present in the real prod version of mongodb, it doesn't make sense to criticize mongodb for it. Also next time RTFM before using a tool you don't know much about.

I feel this is a justifiable defense, if you use a pre-release version of anything you should recognize that you are taking a risk.

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#13

Post by jchrisa »

freetard wrote: post #3
couchdb wrote: post #2

I should make clear that the notice is titled "Notice for 1.0.1" because the 1.0.1 release (due this week) will contain the fix. The bug is confined to 1.0.0.

I hope next time Damien will think twice before insulting other databases for having similar issues: https://twitter.com/damienkatz/status/15444148375

fwiw, the only error Damien made was failing to review some patches other people wrote. Also, this issues is much less serious than the Mongo problems as it's A) localized and B) fixed. Eg it's a bug not a design decision.

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#14

Post by danlynch17 »

jchrisa wrote: post #13
freetard wrote: post #3

Earlier quoted context omitted.

I hope next time Damien will think twice before insulting other databases for having similar issues: https://twitter.com/damienkatz/status/15444148375

fwiw, the only error Damien made was failing to review some patches other people wrote. Also, this issues is much less serious than the Mongo problems as it's A) localized and B) fixed. Eg it's a bug not a design decision.

Errors: - not reviewing - poor testing procedures - new code in 1.0.0????

Why your claim that its not as bad as mongo is crazy and self serving: - poor code quality is MUCH worse than a design you don't agree with. how could anyone trust couch? at least mongo is upfront about their design decisions, whether you agree or not - the couch team has gone on and on recently about how unreliable mongo is, and yet here is this... - there were a number of unanswered questions on mikeal's blog - sadly he took them down - probably because he didn't like them. maybe his couch db lost the data and he couldn't figure out why...

Also - really nice job attacking mongo while you guys have a MAJOR bug... classy and proessional...

Another funny thing - how long has 1.0.0 been out? 3 week or so? and this was just found? so what, there are like 10 people using couch in production?

And i'm sure this will be down-voted by the couch fan boys - but this ridiculousness has to be addressed.

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#17

Post by tbrownaw »

danlynch17 wrote: post #14
jchrisa wrote: post #13

Earlier quoted context omitted.

fwiw, the only error Damien made was failing to review some patches other people wrote. Also, this issues is much less serious than the Mongo problems as it's A) localized and B) fixed. Eg it's a bug not a design decision.

Errors: - not reviewing - poor testing procedures - new code in 1.0.0???? Why your claim that its not as bad as mongo is crazy and self serving: - poor code quality is MUCH worse than a design you don't agree with. how could anyone trust couch? at least mongo is upfront about their design decisions, whether you agree or not - the couch team has gone on and on recently about how unreliable mongo is, and yet here is th…

> And i'm sure this will be down-voted by the couch fan boys - but this ridiculousness has to be addressed.

Or maybe you'll get down-voted for trying to play psychological games on the voters...

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#18

Post by swannodette »

danlynch17 wrote: post #14
jchrisa wrote: post #13

Earlier quoted context omitted.

fwiw, the only error Damien made was failing to review some patches other people wrote. Also, this issues is much less serious than the Mongo problems as it's A) localized and B) fixed. Eg it's a bug not a design decision.

Errors: - not reviewing - poor testing procedures - new code in 1.0.0???? Why your claim that its not as bad as mongo is crazy and self serving: - poor code quality is MUCH worse than a design you don't agree with. how could anyone trust couch? at least mongo is upfront about their design decisions, whether you agree or not - the couch team has gone on and on recently about how unreliable mongo is, and yet here is th…

Pure trolling. New user. Jabs at MongoDB aside, CouchDB has acted quickly and professionally to the kind of rare unfortunate critical bugs that can (and do) happen to software projects. This quality of response creates trust, not diminish it. Shit happens. What matters is that you admit the mistake and fix it as quickly and publicly as possible. Props to CouchDB.

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#19

Post by coffeemug »

Critical bugs are a question of statistics. As the size of the code-base increases, the probability that there is a critical bug in it quickly approaches one. Who would dare say that millions of lines of core Oracle code do not have at least five obscure bugs that cause data loss in some situations?

Re: CouchDB Notice for 1.0.1 - Potential Data Loss

#20

Post by jchrisa »

danlynch17 wrote: post #14
jchrisa wrote: post #13

Earlier quoted context omitted.

fwiw, the only error Damien made was failing to review some patches other people wrote. Also, this issues is much less serious than the Mongo problems as it's A) localized and B) fixed. Eg it's a bug not a design decision.

Errors: - not reviewing - poor testing procedures - new code in 1.0.0???? Why your claim that its not as bad as mongo is crazy and self serving: - poor code quality is MUCH worse than a design you don't agree with. how could anyone trust couch? at least mongo is upfront about their design decisions, whether you agree or not - the couch team has gone on and on recently about how unreliable mongo is, and yet here is th…

The reason the bug took so long to surface is that it is only triggered by an edge case. Most users will not experience issues. After two reports of missing data, the whole team focussed on getting to the bottom of it. This is because we take data integrity seriously.
Post reply on HN