Change Log

• This document covers all releases. For a summary of critical release notices only, see https://docs.datomic.com/release-notices.html.
• Releases with four version number components are bugfix only: releases based on their three-component parents, e.g. 0.8.4020.24 is a bugfix release for 0.8.4020. When upgrading, you should always choose the highest-numbered bugfix release in a family of releases.
• The Datomic Team recommends that you always test new releases in a staging environment first.
• The Datomic Team recommends that you always take a backup before adopting a new release.

• Fix: Correctly deserialize URIs to java.net.URI

• Peer introduces a new dependency on Apache commons-io. If your app has an existing dependency on commons-io, ensure that you depend on 2.15.1 or greater. An older version will cause the peer to throw either a ClassNotFoundExceptionArray when initializing or an IndexOutOfBoundsException when connecting to a database.
• new GcPauseMsec Metric See https://docs.datomic.com/pro/operation/monitoring.html#transactor-metrics
• Fix: Pull expression could return true when supplying a :default for a boolean attribute.
• Fix: Regression introduced in 1.0.6527 that could cause a database with blank keyword idents to fail to load.
• Fix: Datomic could incorrectly calculate the delay for a StorageBackoff, leading to a longer than expected delay before retry.
• Performance: Replace BufferedInputStream with an unsynchronized stream, important for performance on Java 17 and later.
• Enhancement: Provide better error message when d/connect fails to make a connection.
• Enhancement: Increase the number of retries when calling verify-backup on s3 storage.
• Upgraded com.amazonaws/aws-java-sdk-bundle to 1.12.564
• Upgraded com.cognitect/http-client to 1.0.126
• Upgraded com.cognitect/transit-clj to 1.0.333
• Upgraded com.datomic/client-pro to 1.0.77
• Upgraded com.datomic/memcache-asg-java-client to 1.1.0.36
• Upgraded com.google.guava/guava to 32.0.1-jre
• Upgraded org.apache.httpcomponents/httpclient to 4.5.13
• Upgraded org.apache.httpcomponents/httpcore to 4.4.13
• Upgraded org.clojure/core.async to 1.6.681
• Upgraded org.clojure/core.match to 1.0.1
• Upgraded org.clojure/math.combinatorics to 0.2.0
• Upgraded org.eclipse.jetty/jetty-* to 9.4.53.v20231009
• Upgraded org.msgpack/msgpack to 0.6.12
• Upgraded org.apache.activemq/artemis* to 2.31.2

• Upgraded com.cognitect/http-client to 1.0.126
• Upgraded commons-codec to 1.16.0
• Upgraded org.clojure/core.async to 1.6.681
• Upgraded org.eclipse.jetty/jetty-* to 9.4.52.v20230823
• Upgraded org.msgpack/msgpack to 0.6.12

Critical Fixes:

• Fixed regression introduced in 1.0.7010 where query thread pool could deadlock under highly concurrent load, preventing queries from completing.
• Fixed a regression introduced in transactors in 1.0.7010: Peer tx-range can temporarily fail to return a durably-logged transaction coincident with the start of an indexing job until a few more transactions are processed.

• Performance: Improved storage and cache stack performance.
• Performance: Log tree production is now async and separate from transactions.
• Performance: Reduced resources required by indexing.
• Performance: Improved S3 backup and restore performance.
• New CloudWatch metric: TransactionApplyMsec See: https://docs.datomic.com/pro/operation/monitoring.html#transactor-metrics
• New System Property: ddbRequestTimeout See: https://docs.datomic.com/pro/configuration/system-properties.html

• Feature: Separated Garbage Collection Tool for Datomic See: https://docs.datomic.com/pro/operation/capacity.html#separated-garbage-collection
• Fixed regression introduced in 1.0.6725 that disabled health check endpoint.

Fixed regressions introduced in 1.0.6711:

• Nested entities can incorrectly cause a transaction to fail with a `db.error/cycle-in-affinity`.
• Component entities of a transaction entity are all assigned the entity id of the transaction

• The peer and transactor binaries are now licensed under the Apache 2.0 license.
• You do not need to specify a license key in the transactor properties file.
• The peer library is now available under the artifact name com.datomic/peer in Maven Central.
• Any com.datomic support libraries needed by the peer are available in Maven Central.
• The spymemcached library used by Datomic has been shaded to the package name datomic.spy.memcached to avoid conflict with other forks of spymemcached.

• Feature: Implicit partitions. See https://docs.datomic.com/pro/schema/schema.html#implicit-partitions.
• Feature: :db/force-partition and :db/match-partition. See https://docs.datomic.com/pro/transactions/transactions.html#partition-assignment.
• Upgrade: The transactor and peer now require an LTS version of Java 1.11 or greater.
• Upgraded artemis to 2.28.0.
• Upgraded caffeine to 3.1.5.
• Upgraded ring to 1.10.0.

• Performance: Indexing is more aggressive in removing `:db/noHistory` datoms.
• Fix: Transaction no longer times out if a user transaction function puts unfressianable data in an exception.
• Fix: Very rare situation where a transaction could be included in the index but not in the log.
• Upgraded H2 to 2.1.214.

• Feature: io-stats for transactions and queries. See https://docs.datomic.com/pro/api/io-stats.html
• Feature: query-stats for transactions and queries. See https://docs.datomic.com/pro/api/query-stats.html

• Feature: query-stats. See https://docs.datomic.com/pro/api/query-stats.html.
• Performance: Improved performance accessing DDB with high write concurrency.
• Performance: Improved performance accessing S3 with high write concurrency.
• Performance: Improved fressian read.
• Fix: Pull performance regression introduced in 1.0.6527.
• Fix: Exception when using io-stats in nested contexts, you should no longer see "No implementation of method: :-merge-stats of protocol".
• Fix: restart memcached client when needed to work around https://issues.couchbase.com/browse/SPY-196.
• Fix: fail fast if indexing thread is hung waiting on storage response.
• Upgraded postgresql driver to 42.5.1.
• Upgraded AWS libraries to 1.12.358.

• Feature: io-stats for transactions and queries. See https://docs.datomic.com/pro/api/io-stats.html.
• Feature: Verify backups without performing a restore. See https://docs.datomic.com/pro/operation/backup.html#verifying-backups.
• Performance: Improved peer adoption of new indexes.
• Performance: improved performance (throughput and $) for differential backups to S3.
• Performance: Datomic now uses caffeine instead of guava for the object cache.
• Performance improvements for valcache and the object cache.
• Performance: limit thread and memory usage when transactor is adding an AVET index (https://docs.datomic.com/pro/schema/schema-change.html#adding-avet-index).
• Fix: Peer no longer resolves lookup refs before sending tx data to transactor.
• Fix: Attribute names that begin with an underscore can be used for forward lookups in entity and pull. Note that naming attributes with a leading underscore is strongly discouraged because it conflicts with the convention for reverse lookup.

• New API: Add :release-object-cache to d/administer-system. See https://docs.datomic.com/pro/clojure/index.html#datomic.api/administer-system
• New: Expose configuration to set the memcached item expiration in days. https://docs.datomic.com/pro/system-properties.html
• Feature: Support for DynamoDB in additional regions (including eu-north-1)
• Feature: Add support for JDK17
• Notes: Updated EULA
• Upgraded artemis to 2.19.1
• Upgraded com.datomic/memcache-asg-java-client to 1.1.0.33
• Upgraded transit-clj to 1.0.329
• Upgraded aws-sdk-bundle to 1.12.132
• Upgraded client-pro to 1.0.75
• Upgraded clojure to 1.11.0 in transactor

• Upgrade client to 1.0.126

• Fix: Don't print or log connection info by default in peer-server
• Fix: Regression introduced in 1.0.6344 preventing the use of `:db-after` with peer-server.
• Fix: Replace slf4j-nop dependency with slf4j-api
• Upgraded com.datomic/memcache-asg-java-client to 1.1.0.32
• Upgraded embedded REBL to 0.9.242
• Upgraded core.async to 1.5.648
• Upgraded commons-codec to 1.15
• Upgraded Jetty to 9.4.44.v20210927
• Upgraded logback-classic to 1.2.8
• Upgraded org.slf4j libs to 1.7.32
• Upgraded Guava to 31.0.1
• Upgraded AWS Java SDK to 1.12.100
• Upgraded Tomcat-JDBC to 7.0.109

• Upgraded AWS Java SDK to 1.12.100
• Upgraded Jetty to 9.4.44.v20210927
• Upgraded core.async to 1.5.648
• Upgraded core.cache to 1.0.225
• Upgraded data.priority-map to 1.1.0
• Upgraded http-client to 1.0.110

• Upgraded Jetty to 9.4.44.v20210927
• Upgraded logback-classic to 1.2.8

• New API: `Database.dbStats`. See dbStats
• Fix: Prevent a problem where in rare situations indexing jobs can fail repeatedly with an ArityException in the transactor log.
• Fix: Prevent a problem where in rare situations indexing jobs can fail to progress, leading to AlarmBackPressure and operators needing to restart the transactor process.
• Fix: Ensure that d/log is only as recent as d/db.
• Fix: Regression introduced in 1.0.6316 that caused memcache client to fail to start when using SASL authentication.
• Fix: Regression introduced in 1.0.6316 that could prevent reporting of metrics to Cloudwatch
• Fix: Redact memcache password in log data
• Fix: Don't print connection URI to log
• Fix: Don't expose database credentials when printing `db` value
• Change the transactor property `datomic.printConnectionInfo` default to false
• Enhancement: bin/maven-install now installs memcache-asg-java-client to the local maven repository.
• Upgraded Clojure to 1.10.3.
• Upgraded AWS Java SDK to 1.12.1.
• Upgraded Jetty to 9.4.41.v20210516.
• Upgraded ActiveMQ Artemis to 2.17.0.
• Upgraded core.async to 1.3.618.
• Upgraded data.json to 2.4.0.
• Upgraded tools.cli to 1.0.206.
• Upgraded org.fressian to 0.6.6.
• Upgraded transit-clj to 1.0.324.

• Upgraded core.async to 1.3.618.
• Upgraded transit-clj to 1.0.324.
• Upgraded Jetty to 9.4.41.v20210516.

• Upgraded Clojure to 1.10.3.
• Upgraded Jetty to 9.4.41.v20210516.
• Upgraded tools.cli to 1.0.206.

• New feature: AWS memcached auto-discovery See Node Auto Discovery
• Improved performance for query under heavy parallel load.
• Fix: Attribute specs respect `false` values when ensuring attribute existence.

Changed in 1.0.6269

• Fixed intermittent ClassCastException in `:reverse` direction of `index-pull`.
• Improved performance for query under heavy parallel load.
• Improved performance for indexing after excision.
• Upgraded ActiveMQ Artemis to 2.14.0.
• Upgraded guava to 30.1-jre.
• Upgraded Clojure contrib deps to their 1.0.x versions.
• Upgraded org.slf4j libs to 1.7.30.
• Upgraded AWS Java SDK to 1.11.946.

Changed in 1.0.6242

• Fix: Attribute predicates are now applied to assertions only.
• Upgrade to presto 348 for Datomic analytics.

• Improvment: Make client dynaload thread safe

Changed in 1.0.6222

• New: Change the scale of a BigDecimal attribute in a transaction.
• New: Add `:apply-msec` key to `:tx/process` events in the log, useful for identifying slow transactions.
• Upgrade to presto 346 for Datomic analytics.

Changed in 1.0.6202

• New feature: Cancel
• Upgrade: The version of the bundled Presto server is now 338. Note: This upgrade now requires Java 11 to run Presto server.
• Fix: Prevent race condition in valcache that could lead to a failed read
• Fix: Regression introduced in 1.0.6165 that caused Datomic Console to fail to start on recent versions of Datomic.
• Fix: Prevent situation where `tx-range` sometimes returned one extra transaction prior to a specified instant.

• Fix: datomic.api.client.async/client now accepts :dev-local as a :server-type

• Add support for dev-local clients

• Fixed bug that caused Console to fail to start on newer versions of Datomic.

NOTE: This is a stand-alone console release. You can download the console from https://my.datomic.com/downloads/console

• New feature: qseq
• New feature:index-pull
• New feature: pull xform
• Upgrade: The transactor and peer now require Java 1.8 or greater.
• Enhancement: Optimize cache usage of queries that pull
• Enhancement: Improve index efficiency.
• Fix: only read *.edn metaschema files in analytics support
• Updated REST server jetty dependencies from 9.4.24.v20191120 to 9.4.27.v20200227.
• Updated liberator (used in REST server) to 0.15.3.

• New feature: qseq
• New feature: index-pull
• Updated jetty dependencies from 9.4.24.v20191120 to 9.4.27.v20200227.

• New feature: `[:db/retract eid aid]` will retract all values for an eid/aid combination.
• Critical Fix: regression introduced in 0.9.6014 where `datoms`, `seek-datoms`, and `index-range` return incorrect results if `Iterable.iterator` is called more than once on the returned value.
• Fix: respect `nil` as a limit in query `pull` expression.
• Fix: respect `false` as a default in query `pull` expressions for boolean-valued attributes.
• Fix: allow arbitrary `java.util.List` (not just Clojure vectors) for lookup refs.
• Updated REST server jetty dependencies from 9.4.15.v20190215 to 9.4.24.v20191120.
• Updated bundled Presto server from 316 to 329.
• Removed groovy from the transactor distribution. (This was unused except for examples.)

• Eliminate unnecessary peer dependency on core.async and tools.reader introduced in 0.9.6014.
• Fix: `#db/fn` literals preserve `:code` metadata.

• Fix: Prevent a rare scenario where retracting non-existent entities could prevent future transactions from succeeding.
• Update transactor core.async dependency to 0.5.527.

• Enhancement: performance improvement for range predicates in analytics support.
• Enhancement: Many error maps now include the tempid mappings for data that caused a transaction to fail.
• Enhancement: When transactor is unavailable, peer returns an error including a `:cognitect.anomalies/unavailable` category.
• Fix: Improve performance of lookup refs against as-of databases.
• Fix: Include bash shebang in `bin/maven-install`.
• Fix: Report an error on invalid aggregate function names in query.

• New: `index-parallelism` transactor property enables higher index job throughput.

Index Parallelism.

• Fix: prevent exception thrown when handling COUNT(*) clauses in analytics support.
• Fix: resolve tempids for reference attributes inside tuples.
• Fix: do not create redundant `:db.install/attribute` datoms for idempotent schema operations.
• Update transactor Clojure dependency to 1.10.1.

• New feature preview: Analytics.
• Updated AWS library dependency to 1.11.600.
• Expanded the retry window for backup and restore operations. This helps backup and restore jobs complete in the face of transient errors.
• Stopped reporting transaction errors asynchronously.

• Redact password in exception data when peer connection fails.
• Correctly handle boolean attributes in composite tuples.
• Updates to address vulnerabilities in Apache dependencies:
  • Jackson from 2.6.6 to 2.9.9.
  • Logback from 1.0.13 to 1.2.0.
  • Zookeeper 3.4.6 to 3.5.5.

• 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
• New feature: cassandra2
• Vulnerability Fix: Updated Commons Collections from 3.2.1 to 3.2.2. See https://issues.apache.org/jira/browse/COLLECTIONS-580.
• Fix: `sample` aggregate could hang query thread.
• Impoved performance of valcache cleanup.
• Updated REST server jetty dependencies from 9.3.7.v20160115 to 9.4.15.v20190215.
• Updated ActiveMQ Artemis dependencies from 1.4.0 to 1.5.6.

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

• Fix: re-enable memcached support which was inadvertently disabled in 0.9.5783.

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

• New feature: Valcache.
• Fixed cache problem in peer-server where all `d/with` databases deriving from a common initial call to `d/with-db` had the same common value.
• Fixed bug introduced in 0.9.5703 that prevented using class static methods in query function expressions.

• Bugfix: fixed Jetty configuration that could cause a client to prevent JVM from shutting down.
• Upgraded transit-clj to 0.8.313

• Enhancement: added sync to client API. Client Synchronization

• New feature: Classpath Functions. Classpath Functions.

• Release 0.9.5697 fixes two security vulnerabilities in Datomic On-Prem transactors running the free: or dev: storage protocol. https://forum.datomic.com/t/important-security-update-0-9-5697/379.
• Enhancement: New security configuration options for free: and dev: transactors.

• Upgrade: Updated Transactor AMIs for all regions to latest Amazon Linux. Note that per AWS guidelines PV AMIs are no longer provided.
• Added support for eu-west-3 region

• New feature: `:as` and `attr-with-opts` syntax in the pull API.

• Enhancement: Peer server allows arbitrary code in queries.
• Enhancement: Better error messages from peer server.

• Bugfix: Transactors and peers now use disjoint ranges for tempid generation, so tempids generated in a transaction functions cannot collide with tempids generated on the peer.
• Bugfix: Fixed a bug where starting a peer and transactor at about the same time could lead to a string tempid incorrectly unifying with another tempid in the same transaction.

• Bugfix: Fixed bug that prevented healthcheck endpoint from starting on machines with more than 8 cores.

• Bugfix: Stop printing sensitive Cassandra connection information in the log.

• Bugfix: Fixed an HA performance bug where a transactor could continue to write a heartbeat during shutdown, causing up to a 30 second delay before the standby transactor could take over.
• Enhancement: More efficient index use in transaction processing. This will improve write latency and throughput for some update-heavy transaction loads.

• Bugfix: Release 0.9.5561.50 fixes a bug in the catalog that, in the unlikely circumstance where one has deleted a database and restored it from a backup without first having called `gc-deleted-dbs`, can cause a subsequent `gc-deleted-dbs` to delete that (active) database.
• Bugfix: Prevent unbounded thread use by query pool.
• Upgrade: Peers and transactors now use version 1.11.82 of the AWS SDK.
• Upgrade: Updated the AWS regions and instances types available via the CloudFormation template.
• Enhancement: Better error message when unable to resolve an entity.
• Enhancement: Health check endpoints for transactors and peer servers.

• Bugfix: Fixed a bug where peer server could ignore the `basis-t` of a client request, answering queries from the latest db value instead.

• Bugfix: Fixed bug where queries with variables in attribute position could return tuples that differ only by Java representation, e.g. a tuple with Integer 1 and a 'different' tuple with Long 1.
• Bugfix: Fixed a bug where an ident that has been used to name more than one different entity over time could return an outdated entity id from e.g. `d/entid`.
• Improvement: Better performance creating memory databases.

Bugfixes in new functionality introduced in 0.9.5530:

• clients can now query values produced by `with-db`.
• string tempids are now available in the `:tempids` key returned by e.g. `transact`.
• indexing jobs correctly handle the implicit use of `:db.install/attribute` and `:db.alter/attribute`.

• New Feature: Clients and peer server. Clients and Peers and Peer Server
• New Feature: String tempids
• Improvement: `db.install/attribute` and `db.alter/attribute` are now optional.

• Bugfix: Fixed bug introduced in 0.9.5404 where peers do not reconnect after losing transactor connection until the peer makes another call to the transactor.
• Performance improvement for queries where AVET is more selective than VAET.

• Upgrade: the tranactors and the peer now work with the Cassandra 3.1.0 driver.
• Upgrade: the transactor and the peer now use ActiveMQ Artemis 1.4.0. Peers from this release forward -cannot- connect to older transactors. When upgrading to (or past) this release, you must upgrade transactors first.

• Bugfix: Eliminated a bug where, given a particular and extremely unlikely interleaving of indexing failures and transactor successions, some transactions can be incorporated in the log but not in the indexes.
• Bugfix: `:db.fn/cas` now rejects attemps to CAS a cardinality-many attribute.

• Improvement: The `log` API can now be used with the memory database.
• Bugfix: A unique attribute value can now be transferred from one entity to another within a transaction.

• Upgrade: The transactor and peer now use HornetQ 2.4.7. Peers from this release forward -cannot- connect to older transactors. When upgrading to (or past) this release, you must upgrade transactors first.
• Upgrade: Datomic now uses AWS SDK 1.11.6.
• Bugfix: Substantially improved the performance of a corner case involving transactions with a large number of retractions.
• Bugfix: Fixed bug where AVET index could become temporarily unavailable on a recently-added attribute.
• Bugfix: Clojure bigints now work in transaction fns.

• Upgrade: The transactor and peer now require Clojure 1.8.0 or greater.
• Bugfix: Prevent a scenario where not all predicates were applied in queries with a `not` clause.
• Bugfix: Respect `default` specifications in pull expressions containing a wildcard.
• Bugfix: Allow `isComponent` only on ref types in new data, and ignore meaningless `isComponent` specifications on non-ref types in existing data.

• Improvement: All Datomic command line tools now use the standard AWS credentials provider.
• Bugfix: Improved performance of pull + wildcard + since database.
• Bugfix: Fixed bug that could in rare cases cause a peer to be unable to reconnect to a transactor after a transient failure.
• Bugifx: Eliminated a few spurious maven dependencies from peer library.

• Improvement: connection caching behavior has been changed so that peers can now connect to the same database served by two (or more) different transactors.
• Bugfix: it is no longer possible to create a database name that will result in an invalid URI.

• Notice: The full Amazon AWS SDK for Java is no longer shipped with the Datomic peer library. If you are using AWS, see the section in the storage docs about including the AWS SDK for Java for help with configuring your peer with this upgrade: provisioning-dynamo
• New: The transactor and peer now require Clojure 1.7.0 or greater.
• Improvement: Remove dependency on monolothic AWS SDK for Java library.
• Improvement: Add support for eu-central-1
• Improvement: Throw error when `datomic.api/pull` is passed a history db.
• Bugfix: Fixed bug that could cause transactor to report a spurious error message after a successful restore if transactor wasn't running.
• Bugfix: Fixed bug that could, in unusual circumstances, cause a database to fail to load with an NPE in datomic.db-next_valid_inst

• Bugfix: Fixed bug that could cause a transactor to terminate when deleting a database against Cassandra storage.
• Bugfix: Fixed bug where retracting an excision could cause indexing to fail.
• Bugfix: Fixed bug that prevented connecting from a peer that deletes and recreates a database name.

• Bugfix: Eliminated a bug where, given a particular and extremely unlikely interleaving of indexing failures and transactor successions, some transactions can be incorporated in the log but not in the indexes.
• Bugfix: Improved storage garbage tracking.
• Fixed bug that could cause processes using Cassandra driver to hang during peer shutdown.

• Bugfix: Document and enforce limitationsof `:db.type/bytes`.

• Reduced memory and thread use in DDB storage when writing large segments.

• Fixed bug where dropping and re-adding index on an attribute could lead to retracted values reappearing in the AVET index.
• Fixed bug where in rare cases the log API could be temporarily unable to see the most recent transaction.
• Fixed bug where the pull API did not always return all explicit reverse references.

• Improvement: Better error reporting when an invalid entity id is transacted.
• Improvement: Work around a retry bug in Cassandra that can cause unnecessary failures, see https://datastax-oss.atlassian.net/browse/JAVA-764
• Improvement: Preserve ordering of `:db/txInstant`: If the transactor's system clock returns a value older than the time of the most recent tx, use the most recent tx's instant instead.
• Updated to aws-java-sdk 1.9.39.
• Updated to com.datastax.cassandra/cassandra-driver-core to 2.1.5.
• Fixed bug in Pull API when using selectors built from strings.
• Fixed bug that prevented backup/restore from working in previous datomic-free release.

• Improvement: Getting log value from a connection is now much faster.
• Improvement: `restore-db` now prints basis of restored database.
• Improvement: Metrics can now be enabled during backup/restore.
• Fixed bug: `:db.fn/retractEntity` no longer throws an exception when passed an invalid entity identifier.
• Fixed bug where `syncIndex` API future could fail to complete.

• New feature: Query timeout
• Improvement: The datalog engine will now do self-unification within a single clause.
• Improvement: Better semantics for query function `/`: built-in-expressions
• Improvement: Better error reporting when a query attempts to use a non-attribute as an attribute.
• Fixed bug that could cause a recursive query to return an undersized result.
• Fixed bug that could cause restore to fail on a case sensitive file system.
• Fixed bug that could throw a Null Pointer Exception when calling API functions on nonexistent identities.

• Note: We are looking for feedback on this initial release of `not` clauses and `or` clauses described below. The API is subject to change based on this feedback. See this blog post for an overview of the new features: https://blog.datomic.com/2015/01/datalog-enhancements.html
• New feature: not clauses
• New feature: or clauses
• New feature: Require vars in rules
• Improvement: Backing up to the same storage is now differential.
• Performance Enhancement: The query engine will make better use of AVET indexes when range predicates are used in the query.
• Improvement: `Peer.getDatabaseNames` can accept a map for cassandra and SQL storages: getDatabaseNames
• Improvement: Better error messages from invalid transactions.
• Update com.datastax.cassandra/cassandra-driver-core to 2.0.8

• New CloudWatch metrics: `WriterMemcachedPutMusec`, `WriterMemcachedPutFailedMusec` `ReaderMemcachedPutMusec` and `ReaderMemcachedPutFailedMusec` track writes to memcache.
• Improvement: Better startup performance for databases using fulltext.
• Improvement: Enhanced the Getting Started examples to include the Pull API and find specifications.
• Improvement: Better scheduling of indexing jobs during bursty transaction volumes
• Fixed bug where Pull API could incorrectly return renamed attributes.
• Fixed bug that caused `db.fn/cas` to throw an exception when `false` was passed as the new value.

• Improvement: Stronger validation on schema value types and cardinalities.
• Improvement: Better error logging for Cassandra.
• Fixed bug that could cause an exception when using limits in a recursive pull specification.

• New feature: Pull Overview: https://blog.datomic.com/2014/10/datomic-pull.html Docs: pull
• New feature: Query find specifications
• New feature: Query pull expressions
• New: Peer.getDatabaseNames
• New: Peer custom monitoring
• Fixed bug that could cause `Peer.shutdown` to hang.
• Fixed bug that could cause `Peer.createDatabase` to leak threads.
• Fixed bug where nested queries could deadlock.
• Downgraded groovy-all dependency to 1.8.9

• Notice: PostgreSQL is no longer shipped with the Datomic peer library. If you are using PostgreSQL, see the section in the storage docs about JDBC drivers for help with configuring your peer with this upgrade: sql-database
• New: `cassandra-cluster-callback` transactor property for configuring a Cassandra cluster.
• New: Garbage collection for deleted databases.

• New: Transactions now support Clojure bigint literals.
• New: `groovysh.cmd` for Windows.
• Improvement: Better failover handling for high availability.
• Improvement: Better handling of intra-transaction unique identity violations
• Improvement: Provisioning a new Cloud Formation is now idempotent in an AWS VPC.
• Improvement: `Database.attribute` now returns nil for non-existent attributes.
• Improvement: Peers no longer try to reconnect to deleted databases.
• Updated peer library dependencies to the following versions: aws-java-sdk: 1.8.11 cassandra-driver-core: 2.0.6 curator-framework: 2.6.0 groovy-all: 2.3.6 guava: 18.0 postgresql: 9.3.1102 JDBC 4.1 slf4j: 1.7.7 spymemcached: 2.11.4
• Fixed bug that caused DynamoDB Local URIs to ignore AWS credentials
• Fixed bug that could cause `Database.id` to throw an exception against a Cassandra storage.
• Fixed bug that could cause process to hang during peer shutdown.

• New: The transactor and peer now require Clojure 1.6.0 or greater.
• Fixed bug that could cause a transactor to become unresponsive after waking from laptop sleep.

• New: Transactor configuration setting to disable printing of credentials. Specify the boolean system property `datomic.printConnectionInfo` as `false` to disable. Default is true.

  Transactor properties documentation can be found at System Properties

• Fixed bug that prevented nested map `db/id` overrides with string keys.
• Fixed bug that could cause extra sessions to be created against Cassandra storage.
• This release optimizes the repair job introduced in 0.9.4880 to minimize its impact on live systems.

• Fixed bug where some indexed retractions are not enforced. This can cause old values to reappear, or uniqueness constraints to consider retracted values. Upgrading the transactor to this release will repair the problem during the next indexing job.
• Delay accepting V-only bindings in query ordering.
• Provide better error messages when backup/restore directory does not exist.
• Upgraded cassandra-driver-core to 2.0.3. This update fixes a bug in Cassandra that was causing it to leak file descriptors as described in https://issues.apache.org/jira/browse/CASSANDRA-6275.
• Added more logging around keys being written to storage.
• Added an error message when peers see no heartbeat.
• Added better error message when value associated with key is unavailable to be read from storage
• Fixed bug where processes would sometimes prefer an old ident over a new one after a restart.
• SQL storage users can now configure the pool validation query via `datomic.sqlValidationQuery`, default is "SELECT 1".
• Re-enable metrics that were inadvertently disabled in 0.9.4815, e.g. `StorageGetMsec` and `StoragePutMsec`.
• Integrity validations added in newer versions of Datomic no longer prevent loading older non-compliant databases.

• Transactors now use the G1 garbage collector, and require Java 7 or later. (Peers continue to work with Java 6 or later.)
• Database backups to S3 can now use '-encryption sse' to request server-side encryption.
• Better defaults and more configuration options for I/O utilization during backup and restore. The Defaults are now good for most scenarios.
• Updated AMIs across all regions with current Amazon Linux distributions and support for HVM-based instances.
• Added support for more Amazon instance types.
• Prevented race condition in `deleteDatabase` that could tie up a thread writing error messages in the log.
• Fixed bug where peers that were offline during a transaction would not see fulltext for the offline time until next indexing job completes.

• Better protection against retracting schema entities. If you encounter the following error

  java.lang.IllegalArgumentException: :db.error/invalid-install-attribute at datomic.error-arg.invoke(error.clj:55) at datomic.db-install_attribute_hook.invoke(db.clj:1034) at datomic.db-run_hooks-fn__3689.invoke(db.clj:1849)

  then you may have incorrectly retracted a schema entity. Contact support@cognitect.com for assistance recovering from this error.

• Protection against placing non-schema entities in the `:db.part/db` partition. If you see the following error message

  "Only schema components can be installed in partition :db.part/db"

  you will need to correct your program to create non-schema entities in `:db.part/user` or a partition you create.

• Fixed bug that prevented compilation of some `:require` forms in data functions.

• New built-in query expressions: `get-else`, `get-some`, `ground`, and `missing`.
• Added support for memcached-sasl, see Caching for details.
• Allow lookup refs for V position in users of VAET index, including `:db.fn/retractEntity`.
• String representation for Connection no longer throws an exception if connection is closed.

• Re-enable input-bound rule predicates

• Fixes for parallelism in query function expressions.
• Fixes variable-less entity clauses.

Fixed bug where systems using adaptive indexing could become unavailable with the following exception on both transactors and peers:

java.lang.NullPointerException: null at datomic.db-find_last_tx.invoke(db.clj:1875) at datomic.db-db.invoke(db.clj:1885)

All users of adaptive indexing (0.9.4699 or greater) are strongly encouraged to upgrade to this release. Both transactors and peers need to be upgraded, but it's not necessary to upgrade them simultaneously.

This release upgrades the backup format to improve backup capacity against large databases. Datomic now stores backups using a subdirectory structure.

0.9.4724 is able to restore backups taken by previous versions of Datomic. However, previous versions of Datomic will not be able to restore newer backups.

• More query optimizations, keeps single-valued :in clauses at top

• Query optimizations.

• Fixed bug in peer object cache management that could result in OOM errors with large (> 2GB) caches.
• Better error reporting for storage failures.
• Allow configuration of transactor KeyStore and TrustStore to facilitate encrypted communication with Storages.

• New feature: Adaptive Indexing. Overview: https://blog.datomic.com/2014/03/datomic-adaptive-indexing.html Upgrading
• Renamed metric: `AlarmTxStalledIndexing` is now `AlarmBackPressure`.
• Fixed default region in CloudFormation template.

• Upgraded HornetQ dependency to 2.3.17.Final. Due to changes in HornetQ, this release is incompatible with previous releases of Datomic. Both peers and transactors will need to be upgraded together.
• Updated Guava dependency to 16.0.1.

• Fixed bug where adding :db/index sometimes would not take effect. If you encounter this error, upgrade to this release then drop and readd the index.
• Tighter validation around invalid schema changes.

• Prevent out-of-memory errors with very large indexing jobs, particularly those that are adding new AVET indexes.
• Release JDBC resources more aggressively when using SQL storage.

• New feature: lookup refs

• Fixed bug where the transaction tempid would not resolve correctly when used only in value position.
• Fixed bug where peers could leak resources trying to connect to databases that have been deleted.
• More detailed error messages for some invalid transactions.
• Raise enforced level of the total number of schema elements (such as attributes, partitions and types) to be fewer than 2^20

0.9.4532 includes an upgrade to the log format that requires simultaneous update of peers and transactors, and is not compatible with older versions, see below:

This release upgrades the database log to format version 2.

• All peers and transactors in a system must move together to this version or later.
• The transactor and peers are backwards compatible with log version 1 Transactors will automatically upgrade database logs to version 2 when a database is used. The performance cost of this upgrade is negligible and upgrades can be performed against production systems.

• Older versions of the peer and transactor are -not- forward compatible with log version 2, and will report the following error:

  NullPointerException java.util.UUID.fromString

• Downgrading to log version 1 is possible. This release includes a command line tool that can be used to downgrade a database to log version 1:

  bin/datomic revert-to-log-version-1 {your-database-uri}

• Fixed bug where, after a transactor failure, Datomic processes could fail to start with a "Gap in data" exception.
• Fixed performance problem with variance and sttdev query aggregation functions.
• Limited thread use in query.

• Improvements to the REST client.
• Added a GettingStarted.groovy sample in the samples/seattle directory.
• Added SSL support for Riak and Cassandra.
• Improved script for launching transactor to allow for cleaner process management.
• Improved built-in Compare-and-Swap performance.
• Datomic now enforces the total number of schema elements (such as attributes, partitions and types) to be fewer than 32k.

• New Feature: Alter Schema.

This feature breaks compatibility with older versions. Once a schema alteration has been performed on a database, only connect peers and transactors running at least version 0.9.4470 to that database.

• New API: Database.attribute and Attribute
• New APIs: Connection.syncIndex / syncSchema / syncExcise..
• Datomic will now reject some unworkable memory settings, e.g. combinations of memory-index-max and object-cache-max that exceed 75% of JVM RAM.
• Added validation to prevent conflicting unique value assertions within a transaction.
• Fixed bug that prevented Datomic Console from working with Riak or Cassandra storages.
• Better logging for Riak storage.

• Preliminary support for Cassandra Storage.

• Used jarjar to move Datomic's use of Apache Lucene to package names that will not conflict with application use of Lucene.

• Updated to aws-java-sdk 1.6.6.
• Datomic now supports DynamoDB Local as a development-time Storage option.
• Datomic transactions now validate that tempids have a valid partition.
• Fixed bug where some transactions would timeout unnecessarily, even though the work was completed by the transactor.
• Fixed bug where fulltext queries did not find answers in the history database.

• Made transactor more robust against transient SQL storage connection failures.
• Fixed bug where transactor would log a spurious NPE from datomic.hornet during shutdown.

• Fixed a bug in IAM roles support that prevented automatic renewal of role credentials in one case.
• Fixed a bug in the build process that caused the 0.9.4314 version of console to be non-operational.

• IAM roles are now the preferred way to supply credentials when running Datomic in AWS. See Storage to configure a new htransactor using IAM roles. See migrate-to-roles to migrate an hexisting Datomic configuration to use IAM roles.
• The transactor now supports a mechanism for integrating different monitoring services, see the 'Custom Monitoring' section of monitoring
• Updated Riak client to 1.4.2.
• Cloudwatch and custom monitoring now report the count of `RemotePeers`.

• Fixed bug where large excisions could prevent subsequent storage garbage collection.
• Fixed bug where Datomic Pro eval keys did not have access to HA.
• Datomic now verifies Lucene major version without using package reflection (fixes inability to uberjar 4260).
• Updated Fressian dependency to 0.6.5.
• Better error message on nil input to query.

• Make sure Util.read preloads schema-reading helpers, so that schemas can be read prior to touching a database.
• Fixed bug in connection pool validator for Oracle SQL storage.

• New: Datomic Console
• More consistent use of exceptions throughout API.
• Quicker detection of transactor disconnects, reported to peers via exceptions in transaction futures and sync futures.
• Fixed bug in 4215, 4218 that caused `IllegalStateException` when calling `Util.read`.
• Corrected sa-east-1 transactor AMI ID.

• Fixed bug where transaction promises could be garbage collected before a transaction completes, preventing `ListenableFuture` callbacks from firing.

• Improved redundacy elimination. If a transaction presents a datom that is identical (except for tx) to an existing datom, that datom will not be added to the log.

• Updated aws-java-sdk dependency to 1.5.5, discontinued using jets3t.
• Reduced background thread usage in query.
• Transactions now convert doubles to floats when attribute schema requires floats.
• Transactor heartbeat is now more robust in the face of transient failures writing to storage.

• `:db/noHistory` now respected by indexer.
• more precise docstring for `:db/noHistory`.

• Improved transactor performance, specifically around memory usage and GC pauses. This includes improved memory efficiency in indexing, and a new set of GC flags in bin/transactor.
• Fixed bug where queries with constants in V position could return too many results.
• Transactor does more useful logging at INFO level, so there should be less need to modify logging configuration.

• New: API for accessing the log.
• Return correct result from REST avet datoms call when neither start nor end are provided.
• Eliminate spurious file bin/logback-test.xml that was incorrectly included in 0.8.4111.

• New: Memory settings for the transactor must be explicitly specified in the transactor properties file. There are no default settings, so existing transactor property files that lack these settings will no longer work. The transactor properties sample files include three complete examples, representing ongoing usage, one-time imports, and constrained-memory usage during development.
• New: Stricter validation of datoms within a single transaction, preventing duplication of the same datom and multiple assertions of cardinality-one attributes. This will cause transactions that would formerly have succeeded to fail with a validation error.
• New: The transactor and peer now require Clojure 1.5.1 or greater.
• New: Peer configuration setting for peer/transactor connection timeout. Specify system property `datomic.peerConnectionTTLMsec` in milliseconds. Default and minimum are both 10000.
• New: Reverse attribute lookups from an entity are returned as sets.
• Transactors are now more robust in the face of transient errors writing to storage.
• `touch` now works correctly for component entities that have `:db/ident`.
• Better error messages for invalid S3 backup URL, attempting to back up a database that does not exist.
• Updated jetty dependencies (used in REST server).

• Fixed bug that prevented zero-argument data functions in Java.
• Fixed bug where peers have trouble connecting when already-connected peers are producing a heavy write load.

• Fixed bug in 0.8.4020 where nested collections of preexisting entity ids were incorrectly rejected by the transactor, with a "Unable to interpret … as a reference target" message.
• Fixed bug in 0.8.4020 where use of a transaction entity in value position only leads to background indexing failure on the transactor.

• Component entities can now be created as nested maps in transaction data
• Tightened peer HornetQ timeout for faster failover.
• Allow sets as an alternative to lists when specifying values for a cardinality-many attribute in transaction data.
• Fixed bug: Allow the transaction entity to appear in value position only in transaction data.
• Fixed bug: Prevent excessive memory use that would occur before rejecting invalid transaction that attempts to `db.fn/retractEntity` nil.

• Updated several library dependencies to more recent versions: aws, guava, h2, logback, netty, and slf4j.
• Better `toString` representations for objects likely to be encountered in shell (e.g. groovysh) sessions.

• Increased parallelism in query.
• New API: Connection.sync
• Connection.db now returns a database immediately, even if the

transactor is unavailable.

• Improved peer recovery time during HA failover.

• Fixed bug where some active log segments are marked as garbage, which can result in log corruption after a call to `gcStorage`. Moving to this release is strongly advised.
• Improved CloudWatch metric: `IndexWrites` is now reported once per indexing job, making it easier to reason about per-index-job load.
• New CloudWatch metric: `TransactionBatch` tracks the number of transactions batched into a single write to the log.
• New CloudWatch metric: `MemoryIndexFillMsec` reports an estimate of the time to fill the memory index, given the current write load.

(Do not use this release.)

• Fixed bug where indexing jobs could fail for fulltext attributes.

• Fixed bug where HA transactor pool can become stuck and no transactor can start. All HA users should adopt this release as soon as possible.
• Mark log segments as garbage after excision. Note that .gcStorage is still a necessary separate step.
• Improved efficiency writing transaction log.
• Quickly report pending transasctions failed if transactor connection is lost.

• Excision.

• Fixed bug where background index creation could fail to trigger in systems running multiple databases, eventually resulting in need to restart transactor.

• Allow explicit `h2-port` and `h2-web-port` specification in the query string for free and dev protocols.
• Fixed bug where Hornet usage of file system did not respect `data-dir` transactor property.
• Upgraded to netty 3.6.3.Final.

• Enhanced SQL storage to work with a wider set of databases, including Oracle.
• Fixed bug where, after a cold restart of transactor, peer could attempt transactions that would arrive before the transactor was ready and timeout.
• Fixed bug that caused "Database deleted" error when deleting and recreating databases in development.
• Fixed bug in CloudFormation template creation that required explicit setting of `java-opts` property, even when defaults acceptable.
• Added missing AWS instance sizes to CloudFormation template generator.
• Upgraded to AWS Java SDK 1.4.1.

• Fixed incorrect validation introduced in 0.8.3861 that prevented asserting the attribute value `false`.

• New API `Peer.shutdown`
• New API `Connection.release`
• Fixed spurious error after heartbeat failure on transactor.
• New: positional destructuting of datoms (Clojure API).
• Fixed performance problems in `:db.fn/retractEntity`.

• Fixed `Entity.keySet` to return a set of strings.
• Better naming convention for logrotation: `{bucket}/{system-root}/{status}/{time-status-reached}`, where status is "active" or "standby".

• Fixed bug where invalid (non-string) fulltext attribute prevents log ingest.
• New `seekDatoms` and `entidAt` APIs.
• `Heartbeat` and `HeartMonitor` metrics have been replaced by the more informative `HeartbeatMsec` and `HeartMonitorMsec` metrics.
• New `java-opts` option in transactor properties.

• Improved resilience to transient errors in backup/restore.
• Upgrade to netty 3.6.0.Final, fixing SSL race condition that could prevent peers from connecting.
• New `java-xmx` setting in CloudFormation template makes JVM heap configuration more evident.
• Deprecated `StorageBackoff` metric in favor of more explicit `StorageGetBackoffMsec` and `StoragePutBackoffMsec` metrics.

• Prevented aggressive timeout in Peer.connect that could occur when connecting to cold transactor + slow log ingest.
• Allowed peers to ingest log in parallel with ingest on a cold transactor.
• Added LogIngestMsec and LogIngestBytes Cloudwatch metrics. See monitoring for more on metrics.
• Renamed system property `datomic.objectCacheBytes` to `datomic.objectCacheMax` for consistency with other property names. See capacity for more on capacity-related properties.

• Fixed bug that caused intermittent deadlock communicating with storage.
• Reduced memory usage during backup and restore.

• Made default JVM heap sizes for AMI appliance more conservative.
• Set transactor instance name based on CloudFormation template name.
• Include command-line utility JARs that were inadvertently omitted in 0.8.3784.

• Improved indexing performance: lower memory use on the transactor, and higher transaction throughput during indexing jobs.
• New deployment documentation:
• New transactor memory setting `memory-index-threshold`, and expanded documentation at capacity
• Overhauled the metrics reported by the transactor. Learn about the new metrics at monitoring.
• Fixed bug that caused incomplete garbage collection of storage on DynamoDB.

• Fixed bug where deleting a database could cause subsequent indexing jobs of other databases to fail with "No implementation of method: :queue-database-index …"
• New `Alarm` metric is fired whenever the transactor encounters a problem that requires manual intervention.
• Improved indexing performance, particularly for larger string and binary values.

• Improved resilience in the face of unreliable or throttled storages.
• Added write-concurrency setting to transactor properties file, which can be used to limit the number of concurrent writes to storage.
• Added StorageBackoff metric, which records the amount of time spent backing off and waiting for storages.
• Fixed bug where fulltext queries would sometimes seek off the end of an index and throw IOException.

• Upgrade to HornetQ 2.2.21. This change breaks compatibility with older versions, so peers and transactors must be upgraded together.

• Fixed bug in HA support. HA does not work with the three previous releases (3692, 3664, 3655). If you are running a standby transactor for HA, make sure to upgrade to this release.

• Fixed bug where restore would restore to a version other than the most recent in the backup storage.
• Improved backup CLI: You can now `list-backups` to see different points in time (t) that are backed up to a storage, and pass a `t` argument to `restore-db` to restore from a version other than the most recent in the backup storage.
• Fixed bug: all transaction errors now throw exceptions consistent with the API documentation. (Some errors had been throwing early, on transact, rather than on dereferencing the transaction future.)
• Fixed bug where a portion of the history index was not considered by the `asOf` database filter.
• Fixed bug where, under unusual circumstances, datoms could reappear in the present index, even though they had been retracted.
• Performance optimization: Peer cache now reads ahead on indexes.
• Updated to spymemcached 2.8.9.
• Fixed bug where retraction of a nonexistent fulltext attribute value could cause subsequent indexing jobs to fail.
• Fixed bug that could prevent connection to a database after a cycle of create / backup / delete / restore.

• Added gap-detection validation when reading log on startup.

  Operating with a gap, while not resulting in loss of data, can cause violations of uniqueness and cardinality constraints. Users on releases prior to 0.8.3664 are strongly encouraged to move to 0.8.3664 or later as soon as possible.

• Fixed bug where entities could have more than one :db/fn attribute.
• Fixed bug in log loading where a window of data could be invisible on restart, even though that data is present in the log.

• Fixed bug where database indexing fails after a backup/restore cycle.
• Fixed bug in Clojure API where transaction futures sometimes would return (rather than throw) an exception.
• Fixed bug in Java API where transaction futures would occasionally return an object that is not the documented map.
• Better error reporting for some kinds of invalid queries.
• alpha support for CORS in the REST service. Note that the bin/rest args have changed. See rest] for details.

• Fixed bug where first restore of a database to a new storage did not include the most recent data, even though that data was present in the backup. (Subsequent restores were unaffected).
• Queries now take a :with clause, to specify variables to be kept in the aggregation set but not returned.
• Database.filter predicates now take two arguments: the unfiltered Database value and the Datom.
• You can now retrieve the Database that is the basis of an entity with Entity.db.
• You can now install a release of Datomic Pro into your local maven repository with bin/maven-install.

• Alpha release of Database.filter, which returns a value of the database filtered to contain only the datoms satisfying a predicate.
• New AWS metric: IndexWrites.
• Peers no longer need to include a Datomic-specific maven repository, as Fressian (https://github.com/Datomic/fressian) is now available from Maven Central and clojars.

• Added memory-index-max setting to allow higher throughput for e.g. import jobs.
• Bugfix: Fixed bug that prevents indexing jobs from completing with some usages of fulltext attributes.
• Added additional AWS instance types to AMI setup scripts.
• Bugfix: Cloudformation generation now respects aws-autoscaling-group-size setting.
• Fixed broken query example in GettingStarted.java.
• Fixed docstring for datomic.api/with.

• Fixed "No suitable driver" error with dev: and free: protocols in some versions of Tomcat.
• Updated bin/datomic `delete-cf-stack` command to work with multiregion AWS support.

• Fixed bug that prevented building queries from Java data.
• Transactor AMIs are now available in all AWS regions that support DynamoDB: us-east-1, us-west-1, us-west-2, eu-west-1, ap-northeast-1. and ap-southeast-1.
• Breaking change: CloudFormation properties file has a new required key `aws-region`, allowing you to select the AWS region where a transactor will run.

• Preliminary support for Couchbase and Riak storages.
• Breaking change: DynamoDB storage is now region-aware. URIs include the AWS region as a first component. The transactor properties file has a new mandatory property `aws-dynamodb-region`.
• Breaking change: CloudWatch monitoring is now region-aware. If using CloudWatch, you must set `aws-cloudwatch-region` in transactor properties.
• Transactions now return a datomic.ListenableFuture, allowing a callback on transaction completion.
• Fixed bug in the command line entry point for restoring a database, which was defaulting to the most ancient backup instead of thre most recent.
• Fixed bug that prevented restoring to a `dev:` or `free:` storage in some situations.

• Breaking change: db.with() now returns a map like the map returned from Connection.transact().
• Incompatible and unsupported schema changes now throw exceptions.
• Better error messages when calling query with bad or missing inputs.
• Documented system properties.

• Fixes to alpha aggregation functions.

• Alpha support for aggregation functions in query.

• Fixed bug where variables bound by a query :in clause were not seen as bound inside rules.
• Added `invoke` API for invoking database functions.

• Fixed bug that caused temporary ids to read incorrectly in transaction functions, causing transactions to fail.

• Fixed but that prevented catalog page from loading on REST service when running against a persistent storage.
• Enhancements to REST documentation.

• The REST service is now its own documentation. Just point a browser at the root of the server:port on which you started the service. Note that the "web app" that results is the service. It is not an app built on the service, nor a set of documentation pages about the service. The URIs, query params, and POST data are the same ones you will use when accessing the service programmatically.

• Initial version of REST service.

• new API: `Entity.touch` touches all attributes of an entity, and any component entities recursively.

• Fixed bug where some recursive queries return incorrect results.
• Fixed bug in command-line entry point for restoring from S3.

• Fixed bug where peers could continue to interact with connections to deleted databases.
• Fixed query bug where constants in queries were not correctly joined with answers.
• Fixed directory structure in JAR file format, which was causing problems for some tools.
• Report serialization errors back to data function callers, rather than make them wait for transaction timeout.
• Better error messages for some common URI misspellings.

• Fixed bug in :db/txInstant that prevented backdating before db was created.

• new API: `Peer.resolveTempid` provides the actual database ids corresponding to temporary ids submitted in a transaction.
• changed API: You can now explicitly specify the :db/txInstant of a transaction. This facilitates backdating transactions during data imports.
• changed API: Transaction futures now return a map with DB_BEFORE, DB_AFTER, TX_DATA and TEMPIDS.
• changed API: Transaction report queues now report the same data as calls to `Connection.transact`
• changed API: Transaction report TX_DATA now includes retractions in addition to assertions.
• new API: `Database.basisT` returns the t of the most recent transaction
• Bugfix: fixed bug that prevented AWS provisioning scripts from running

• new API: `Database.history` returns a value of a database containing all assertions and retractions across time
• new API: `Database.isHistory` returns true if database is a history database
• new API: `Datom.added` returns true if datom is added, false if retracted
• changed API: the Datom relation in a query now exposes a fifth component, containing a boolean that is true for adds, false for retracts
• changed API: removed `Index` class, range capability now available directly from `Database`
• Bugfix: calling `keys` on an entity with no current attributes no longer throws NPE
• udpated to use recent (12.0.1) version of Google Guava
• when a peer calls `deleteDatabase`, shutdown that peer's connection

• fixed bug where some recursive queries returned partial results
• simplified license key install: pro license keys are installed via a `license-key` entry in the transactor properties file
• connection catalog lookup is cached, so it is inexpensive to call `Peer.connect` as often as you like
• improved fulltext indexing and query performance

• changed API: query clauses are considered in order
• changed API: when navigating entities, references to entities that have a `db/ident` return that ident, instead of the entity
• new API: `Database.index` supports range requests
• fixed broken dependency that prevented datomic-pro peer jar from working with DynamoDB
• new API: `Peer.part` function returns the partition of an entity id
• new API: `Peer.toTx` and `Peer.toT` conversion functions
• entity equality is ref-like, i.e. identity-based
• eliminated resource leaks that affected multiple databases and some failover scenarios

• added API entry points for generating semi-sequential UUIDs, a.k.a squuids
• use correct maven artifact ids: `datomic-free` for Datomic Free Edition, and `datomic-pro` for Datomic Pro Edition
• fixed bug where queries could see retracted values of a cardinality-many attribute

Initial public release of Datomic Free Edition and Datomic Pro Edition