NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



The Three Ways to Remove a Document From CouchDB and Their Usages

Nathan Vander Wilt:

The choice depends (mostly) on how you’re syncing between databases:

  • With filtered replication, you might want to add _deleted:true alongside the original document data
  • For normal/plain/unfiltered replication, you can simply DELETE
  • If you are NOT replicating, _purge has its uses

I only knew about the straightforward DELETE approach. But I’m learning that it is just a special case of marking a document as deleted. While the post looks at these operations from the point of view of CouchDB’s masterless replication, their behavior can also be connected to the school of soft deletes or Pat Helland’s non updatable data:

In large-scale systems, you don’t update data, you add new data or create a new version.

Original title and link: The Three Ways to Remove a Document From CouchDB and Their Usages (NoSQL database©myNoSQL)