Datomic Cloud Releases

• Enhancement: allow for the inclusion of the target dir in the :paths list.

• New: Upgrade from t2 to t3 instances for bastion and query groups.
• Fix: tx-range now returns a map with a :data key, consistent with the docs.
• Fix: Correctly handle boolean attributes in composite tuples.
• Fix: Prevent erroneous attempts to use Datomic On-Prem's excision feature.

• Fixed problem where databases that change an attribute from `:db.cardinality/one` to`:db.cardinality/many` may become unavailable after a process restart.

• New feature: Tuples.
• New feature: Attribute predicates.
• New feature: Entity specs.
• New feature: Return maps.
• Fix: `sample` aggregate could hang query thread.

• New feature: Return Maps.
• New feature: Reverse references in nav (try it in REBL).

• Improvement: Fixed issue where some older Java libraries could not be loaded in an ion application

The 477-8741 release contains fixes, enhancements, and dependency updates:

• Enhancement: HTTP Direct integration for ions.
• Enhancement: Improved integration between ions and AWS Network Load Balancers. This eliminates transient errors during rolling deployments.
• Enhancement: Improved integration between ions and AWS Lambda. This also eliminates transient errors.
• Fix: Issue where cluster nodes could become unresponsive when serving multiple databases or a burst of `tx-range` queries.
• Fix: Nested queries could deadlock the query pool on Solo nodes.
• Fix: Increased direct memory on Production nodes to prevent out-of-direct-memory errors.
• Update: Version 1.7.26 of org.slf4j libraries.

• New Feature: HTTP Direct
• Enhancement: Improved integration between ions and AWS NLBs

Note Our Cloud Formation templates use node.js lambdas to create support functions for Cloud Formation. April 30th 2019 is the end of life date for AWS Lambda node.js runtime that we currently use.

Effective May 1, 2019, Datomic Cloud CloudFormation templates older than 4/25/2019 will no longer execute. Datomic systems launched with those templates will continue to run, but any template operations (launching or upgrading CloudFormation stacks) will fail.

All Datomic Cloud users should upgrade to 470-8654.1 at their earliest convenience.

For more information see the AWS runtime support policy.

• Critical: Updated to Node.js 8.10 runtime. All Datomic Cloud users should upgrade at their earliest convenience.

Note If you have created a VPC Endpoint using the provided CloudFormation Template, you will need to delete that CloudFormation Stack prior to upgrading to this version of Datomic Cloud.

Attempting to upgrade to or past this release without deleting the Stack will result in a failed update with the message: Export <SystemName>-VpcEndpointServiceName cannot be deleted as it is in use by <SystemName>-vpc-endpoint

See the troubleshooting documentation for more informaton.

The 470-8654 release contains fixes, enhancements, and dependency updates:

• Fix: Production nodes now use the documented -Xss values for starting the JVM, preventing stack overflow when compiling complex ion applications.
• Fix: Fixed bug where ion connections could fail to become aware of recent transactions in a timely manner.
• Fix: Allow bigint values in transaction data.
• Fix: Corrected whitelist handling of function calls from datalog rules.
• Enhancement: New AWS Region - ap-southeast-1.
• Enhancement: Improved valcache cleanup algorithm.
• Enhancement: Reduce storage overhead of transactions.
• Enhancement: Defer creation of VPC Endpoint Service until specifically needed for cross-VPC client access.
• Update to version 2.9.8 of Jackson.
• Update to version 1.11.479 of the AWS SDK for Java.

The 454-8573 release contains a number of performance and availability enhancements:

• Enhancement: You can configure systems to preload a database before serving requests, eliminating a source of unavailable anomalies.
• Enhancement: Ion deployments load active databases before serving requests, eliminating a source of unavailable anomalies.
• Enhancement: Improved throughput for transactions initiated by ion applications running the Production Topology.
• Enhancement: Improved performance for systems that create and delete many databases (e.g. test systems)
• Enhancement: Improvements to logging.

• Enhancement: Increase CodeDeploy timeout to 5 minutes.
• Enhancement: Include doc strings for user facing functions in build artifact

• Add compatibility with com.cognitect/aws-api
• Add Datafy
• Upgraded http-client to 0.1.87
• Improved error reporting

Release 441-8505 includes critical updates. All users of the Production Topology and Query Groups should upgrade to 441-8505 immediately. The Solo Topology is not affected.

• Critical: fixes a problem that can cause portions of the log to become inaccessible. Please update as soon as possible.

• New feature: query groups.
• New instance type option: i3.xlarge for Production.
• Improved memory settings: more stack space for Solo, more heap space for Production.
• Bugfix: fixed bug that could prevent a Production node from beginning indexing jobs.

• Bugfix: fixed bug that could cause a with database query to go to the wrong node in a production cluster.
• Bugfix: fixed Jetty configuration that could cause a client to prevent JVM from shutting down.
• Upgraded transit-clj to 0.8.313
• :query-group parameter is no longer required in the client arg-map

• Enhancement: parameters library for working with the AWS Systems Manager Parameter Store

• Bugfix: allow retraction of :db/unique attributes
• Bugfix: coerce Integer values to long when needed in transactions
• Enhancement: better memory utilization allows larger query results
• Enhancement: automatically rollback deployments when an ion application fails to load
• Added support for ap-southeast-2 (Sydney) region

• New Feature: datomic.ion.cast library for monitoring ions
• Bugfix: fixed race condition in ion code loading that could allow ion invocation before namespace completely loaded
• Enhancement: warn on dependency conflicts
• Improvement: prefer shell-friendly symbols instead of strings as arguments to datomic.ion.dev CLI commands
• Improvement: better error messaging when deploying to the wrong region.
• Improvement: list available deploy groups in push output
• Improvement: enforce the requirement for :uname when project has a :local/root in deps.edn.

• Enhancement: added sync to client API. See https://docs.datomic.com/cloud/whatis/client-synchronization.html
• Better error message when unable to connect to cluster or proxy.

• Upgraded AWS libs to 1.11.349
• Upgraded Jackson libs to 2.9.5
• Fixed cache problem where all d/with databases deriving from a common initial call to d/with-db had the same common value.

• Enhancement: added :server-type :ion
• Enhancement: ensure recentness of d/db conn

• Enhancement: Datomic Ions
• Improvement: Replaced Application Load Balancer with Network Load Balancer. If your applications run in a separate VPC you will need to configure a VPC endpoint.

• Bugfix: doubles and floats allowed in transactions
• Bugfix: avoid unnecessary ":AdopterSkippedOlder" alert when creating new database
• Update: latest Amazon Linux patches
• Improvement: better error handling in Storage template
• Improvement: reduce memcached timeout