Microfiber 16.03

Milestone information

Project:
Microfiber
Series:
trunk
Version:
16.03
Released:
 
Registrant:
Jason Gerard DeRose
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon microfiber-16.03.0.tar.gz (md5, sig) tarball 13
last downloaded 10 days ago
Total downloads: 13

Release notes 

The Microfiber CouchDB replicator has been refined and a number of missing missing unit tests were added:

http://bazaar.launchpad.net/~microfiber/microfiber/trunk/view/head:/microfiber/replicator.py

Although the replicator isn't yet considered part of the stable API and might still undergo breaking API changes, the implementation is mature and is well proven under real-world use.

Some key changes in logging and behaviour:

* `replicate_one_batch()` now logs the number of documents that were missing on the dst_node for this particular batch, making it clearer when documents actually needed to be replicated vs when for that batch all of some of the documents were already present on the dst_node; logging wise, this makes the overall replication behaviour easier to understand when doing multi-master, bi-directional replication

* Although `replicate_one_batch()` still replicates in batches of 50 documents, `save_session()` now only saves a new replication checkpoint when the update_seq has advanced by at least 200 since the last checkpoint; especially when doing multi-master, bi-directional replication, this helps reduce the load on CouchDB because `dst.post(None, '_ensure_full_commit')` only needs to be called every 200 updates, whereas previously `replicate()` would save a checkpoint every 50 updates (whether or not new documents were missing on the dst_node)

* `replicate_continuously()` now likewise uses `save_session()` to checkpoint the replication every 200 updates, which means fewer changes need to be re-processed when a replication session is restarted and `replicate()` steps through the changes backlog

Changelog 

This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.