Thursday Apr 10, 2014

CouchDB Weekly News, 10 April

Releases

Apache CouchDB 1.5.1 released

Blog Posts

Major Discussions

Writing many docs at once: bench marking a 10k write to a CouchDB server (see thread here)

Question about "complex" range queries (see thread here)

Is the revision field deterministic? (see thread here)

CouchDB Universe

Apache Con has taken place from April 7-9. You can find the slides of the talks given here

Releases in the CouchDB Universe

New Erlang Version is out

mbtiles2couchdb, for using CouchDB as a simple tiles server

RCouch has a new home: announcement | the new home

PPnet, a minimal social network to drop into websites based on PouchDB

sabisu, a sensu web UI, got open sourced by Cloudant last week

Janus, an online storage for offline Web Apps built using PouchDB

couche 0.0.2, a couchdb client for node, with specific apis

mock-couch, an http server pretending to be couchdb, for unit testing

couchdb-sync 0.1.1 - a generic couchdb replicator which is basically an eventemitter

hackoregon-couch 0.0.2 which exports database information from PostgreSQL and imports into CouchDB

overwatch 0.2.7, a deterministic couchdb replication watcher

Opinions

Use Cases, Questions and Answers

Get Involved!

here's a list of beginner tickets around our currently ongoing Fauxton-implementation. If you have any questions or need help, don't hesitate to contact us in the couchdb-dev IRC room (#couchdb-dev) – Garren (garren) and Sue (deathbear) are happy to help.

Your help on updating CouchDB-Python for Python 3. Wanna join? Please participate here.

New PMC Member

Joan Touzet joins the Apache CouchDB Project Management Committee today. Joan has made outstanding, sustained contributions to the project. Welcome to the Couch, Joan!

Events

April 10, Berlin, Germany: CouchDB Hack Night

Job opportunities

… and also in the news

This is a security release. Download link A discussion around handling and measurements of bulk input in CouchDB.Requirements for sort orders of data views.Quoting Robert Samuel Newson's reply : "Yes, it’s deterministic. The same document with the same history will have the same _rev value. This is an optimization over the previous algorithm where _rev was a random UUID. […] The advantage is that two servers receiving the same update can more optimally replicate. They still have to check that the target has all _id/_rev pairs but will usually be able to skip actually transmitting document and attachment content."If you want to get into working on CouchDB:We'd be happy to have you!Posted on behalf of Lena Reinhard.

Posted at 10:59AM Apr 10, 2014 by Noah Slater in News | |