Release Notes - FaunaDB 2.6.1

Released 01/31/2019

The Fauna team is pleased to announce the patch update release of FaunaDB 2.6.1. Release 2.6.1 supports rolling updates from the previous 2.6.0 release. The release is available for download now.

If you are running FaunaDB version 2.5.4 or prior, you must upgrade to 2.5.8 first and then upgrade to 2.6.1. If you need assistance with the upgrade, contact support@fauna.com.

New features

  • With operational simplicity in mind, a FaunaDB cluster can automatically recover in the presence of massive IP address changes.

    IP address changes are not common, but development and test environments are often shut down regularly to reduce recurring cloud costs. Restarts can cause nodes to acquire new IP addresses, and could cause communication failures in affected FaunaDB nodes that would prevent the nodes from joining the cluster.

    FaunaDB 2.6.1 brings resiliency to this process and ensures that clusters automatically recover, even if a majority of nodes undergo IP address changes.

  • The replica-level "Read Your Own Write" guarantees are now stronger due to write acknowledgement improvements that help to prevent stale reads.

Enhancements

  • Tuned RAFT implementation to improve cluster recovery speed when a replica is lost.

  • By default, indexes can no longer be used in the same transaction that they are created in. If you know that the index is going to be empty, you can set active when creating the index to make it usable immediately.

  • The maximum results page size has been increased. Previously you could only receive up to 1,024 rows. FaunaDB can now return up to 100,000 rows.

  • The topology stabilization time for new clusters, or clusters that have lost a replica, has been greatly improved.

List of issues fixed

  • Fixed a bug where a Lambda function that took no arguments was dropped and replaced with an empty object.

  • Instance data can now be accessed with Select().

  • More precise errors are now reported when creating a class with a reserved name.

  • Ensured that FaunaDB renders event sources in historical sets with events.

  • Ensured that selecting id from instance in events works properly.

  • User defined functions can no longer call other user defined functions.

  • FaunaDB now emits Fauna is ready to the console after the cluster is initialized.

Next Steps

Learn more about FaunaDB from our product page.

Was this article helpful?

We're sorry to hear that.
Tell us how we can improve! documentation@fauna.com

Thank you for your feedback!