releases: All content tagged as releases in NoSQL databases and polyglot persistence
After a short break, Terrastore has published a new version, 0.8.0, which brings quite a few interesting features, plus some performance, scalability, and stability enhancements:
- map/reduce processing
- active event listeners
- adaptive ensemble scheduling
- document and communication compression
Sergio Bossa, Terrastore lead developer, has shared more about this release ☞ here:
Terrastore map/reduce implementation targets all documents, or just a subset of documents specified by range, belonging to a single bucket, and is based on three phases: mapper, combiner and reducer. The mapper phase is initiated by the node which received the map/reduce request, the originator node: it locates the target documents and the nodes that hold them, then sends the map function to those node so that it can be applied in parallel on each node; the map function will take each target document as input argument, and return, for each document, a map of
pairs as output. Then, each remote node runs the combiner phase, aggregating its local map results and returning a partial map of pairs. Finally, the originator node runs the reducer phase, aggregating all partial results.
You can download the new Terrastore from ☞ here.
OrientDB, the document or graph store, has announced a new release, 0.9.24, featuring amongst a few SQL support improvements, synchronous and asynchronous replication.
- Support for Clustering with synchronous and asynchronous replication
- New SQL
SELECT FROM ... WHERE ... RANGE <from> [,<to>]
- New SQL
SELECT FROM ... WHERE ... LIMIT 20
- New console command
- New console command
- MRB+Tree now is faster and stable
- Improved import/export commands
- Improved JSON compliance
- Improved TRAVERSE operator with the optional field list to traverse
I’ve contacted Luca Garulli, OrientDB main developer, for more details about the OrientDB replication.
Original title and link: OrientDB New Release Featuring Sync and Async Replication (NoSQL databases © myNoSQL)
In a post yesterday about NoSQL comparisons, I was asking when was the last Tokyo Cabinet release. It looks like from that family of products, the ones going forward are Kyoto Cabinet and Kyoto Tycoon as Mikio Hirabayashi ☞ has announced on Twitter the release of Kyoto Cabinet 1.2.5 and Kyoto Tycoon 0.9.9:
released Kyoto Cabinet 1.2.25 and Kyoto Tycoon 0.9.9, which feature asynchronous replication!
Original title and link: New versions of Kyoto Cabinet and Kyoto Tycoon Released (NoSQL databases © myNoSQL)
After being available only on Windows and Linux, now InfiniteGraph has released a version for Mac OS X 64bit. You can get it from ☞ here. As far as I know the guys at InfiniteGraph are working on a friendlier licensing model for developers.
Update: Cassandra 0.6.8 was pushed out to address a regression bug in Cassandra 0.6.7
- fix read repair regression from 0.6.7 (CASSANDRA-1727)
- Update windows .bat files to work outside of main Cassandra directory (CASSANDRA-1713)
- more-efficient read repair (CASSANDRA-1719)
Getting closer to 0.7, Cassandra has released version 0.6.7. From the ☞ changelog:
- quorum read optimization (CASSANDRA-1622)
- update GC settings in cassandra.bat (CASSANDRA-1636)
- fix hinted handoff replay (CASSANDRA-1656)
- log type of dropped messages (CASSANDRA-1677)
- initMetadata wasn’t loading saved partitioner from disk (CASSANDRA-1638)
- log tpstats when dropping messages (CASSANDRA-1660)
- Avoid dropping messages off the client request path (CASSANDRA-1676)
- fix jna errno reporting (CASSANDRA-1694)
- add friendlier error for UnknownHostException on startup (CASSANDRA-1697)
- add —skip-keys option to stress.py (CASSANDRA-1696)
You can download Cassandra from ☞ here.
Speaking of releases, Redis has announced version 2.0.4, a minor bug fix release:
HMGETused to crash when called against a key that was not holding an hash
- Redis will now not try to save the DB if no save points for RDB are configured, when used as a non persistent cache
The latest Cassandra release seems to be focusing on improving operational aspects. Jonathan Ellis, Cassandra project lead, covers the changes in Cassandra 0.6.6:
- Configurable IndexInterval: Instead of b-trees, Cassandra uses a more i/o-efficient design to find row location […]
- Add CMSInitiatingOccupancyFraction=75 and UseCMSInitiatingOccupancyOnly to default JVM options: By default the JVM tries to estimate when it needs to begin a major compaction to strike a balance between on the one hand wasting CPU by performing GC before it was necessary and on the other running out of heap space before it can finish the collection, forcing it to fall back to a stop-the-world collection
- Document DoConsistencyChecksBoolean option to disable Read Repair: Read repair is how Cassandra restores consistency in frequently-accessed data after downtime of one or more replicas.
- Use JNA to take snapshots: We introduced the use of JNA in 0.6.5 to perform OS-specific optimizations. Here, we’re using it to create the hard links; if JNA is not available, Cassandra will fall back […]
- Add memtable, cache information to GCInspector logs: It turns out that logging information after a garbage collection run is a good way to get bare-bones monitoring information when nothing better is configured.
- Cache save and load: For 0.6.6 we introduced periodic saving of the row and/or key caches to be reloaded at the next restart.
- Tombstone removal during non-major compactions: Now Cassandra takes advantage of the bloom filter that we already use to avoid doing index lookups in sstables that don’t contain any data for a row.
Recently, Riptano, the company focused on Cassandra support, has worked on updating Cassandra documentation. The new docs can be found ☞ here. The part that confuses me a bit is why aren’t these hosted on the Cassandra’s website.
Original title and link: Cassandra 0.6.6 Released Featuring Improvements for Operations (NoSQL databases © myNoSQL)
Big day for Membase (the company, ex Northscale) announcing the release of Membase (the product) 1.0. First time we’ve heard about it was end of July when we took a look at what is Membase. At that moment we’ve also learned that one of the companies using Membase is Zynga (nb Zynga is also a Membase contributer).
Now, 3 months later we have Membase 1.0 release
 coming in two flavors:
- Membase Server Enterprise Edition is a certified distribution of Membase, available for download and purchase at membase.com. Annual product subscriptions start at $999 per node, granting a software use license and access to the Membase Network, which delivers software upgrades, hot fixes, maintenance releases and product support.
- Membase Server Community Edition is a community binary, downloadable at membase.org, where developers can also access and contribute to the source code.
By checking the “supporting quotes” section of the announcement, I’m also noticing a couple of other Membase users: ShareThis, NaviNet, Loggly. So hopefully soon we will also have some case studies.
Correction: This general availability release of Membase has version 1.6, but it is still the first production ready release of Membase.
A new recommended upgrade for MongoDB 1.6 production ready version:
Original title and link: MongoDB 1.6.3 Released, Production Version, Recommended Upgrade (NoSQL databases © myNoSQL)