Softpedia >Windows >Programming >Components & Libraries >Datomic >  Changelog

Datomic Changelog

What's new in Datomic 0.9.5173

May 13, 2015
  • 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 in Datomic 0.9.5153 (Mar 23, 2015)

  • New feature: Query timeout
  • Improvement: The datalog engine will now do self-unification within a single
  • clause.
  • Improvement: Better semantics for query function `/`
  • 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.

New in Datomic 0.9.5130 (Jan 13, 2015)

  • 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.
  • 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.
  • Improvement: Better error messages from invalid transactions.
  • Update com.datastax.cassandra/cassandra-driver-core to 2.0.8

New in Datomic 0.9.5078 (Nov 26, 2014)

  • 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.

New in Datomic 0.9.5067 (Nov 26, 2014)

  • 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 in Datomic 0.9.5052 (Oct 31, 2014)

  • New feature: 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

New in Datomic 0.9.4956 (Oct 13, 2014)

  • 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:
  • http://docs.datomic.com/storage.html#sql-database
  • New: `cassandra-cluster-callback` transactor property for configuring a
  • Cassandra cluster.
  • See http://docs.datomic.com/storage.html#cassandra
  • New: Garbage collection for deleted databases.
  • See http://docs.datomic.com/capacity.html#garbage-collection-deleted
  • 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 in Datomic 0.9.4899 (Sep 13, 2014)

  • 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 in Datomic 0.9.4880.2 (Aug 14, 2014)

  • This release optimizes the repair job introduced in 0.9.4880 to minimize its impact on live systems.

New in Datomic 0.9.4880 (Aug 12, 2014)

  • 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
  • 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.

New in Datomic 0.9.4815.12 (Jun 24, 2014)

  • Fixed bug where processes would sometimes prefer an old ident over a new one after a restart.

New in Datomic 0.9.4815.10 (Jun 18, 2014)

  • 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.

New in Datomic 0.9.4815 (Jun 6, 2014)

  • 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.
  • 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 in Datomic 0.9.4766.11 (May 22, 2014)

  • 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.
  • 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 in Datomic 0.9.4766 (May 22, 2014)

  • New built-in query expressions: `get-else`, `get-some`, `ground` and `missing`. See
  • Added support for memcached-sasl
  • 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

New in Datomic 0.9.4755 (Apr 24, 2014)

  • Re-enable input-bound rule predicates

New in Datomic 0.9.4752 (Apr 23, 2014)

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

New in Datomic 0.9.4745 (Apr 22, 2014)

  • 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.

New in Datomic 0.9.4724 (Apr 17, 2014)

  • 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.

New in Datomic 0.9.4718 (Apr 16, 2014)

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

New in Datomic 0.9.4714 (Apr 15, 2014)

  • Query optimizations.

New in Datomic 0.9.4707 (Apr 9, 2014)

  • 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 in Datomic 0.9.4699 (Mar 25, 2014)

  • New feature: Adaptive Indexing.
  • Renamed metric: `AlarmTxStalledIndexing` is now `AlarmBackPressure`.
  • Fixed default region in CloudFormation template.

New in Datomic 0.9.4609 (Mar 14, 2014)

  • 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.

New in Datomic 0.9.4532 (Feb 8, 2014)

  • 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.

New in Datomic 0.9.4497 (Jan 30, 2014)

  • 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 in Datomic 0.9.4470 (Jan 24, 2014)

  • 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
  • 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

New in Datomic 0.9.4353 (Dec 13, 2013)

  • 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.

New in Datomic 0.9.4331 (Dec 11, 2013)

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

New in Datomic 0.9.4314 (Nov 26, 2013)

  • IAM roles are now the preferred way to supply credentials when running Datomic in AWS.
  • The transactor now supports a mechanism for integrating different monitoring services
  • Updated Riak client to 1.4.2.
  • Cloudwatch and custom monitoring now report the count of RemotePeers`.

New in Datomic 0.8.4270 (Nov 20, 2013)

  • 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.

New in Datomic 0.8.4254 (Oct 30, 2013)

  • 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.

New in Datomic 0.8.4218 (Oct 12, 2013)

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

New in Datomic 0.8.4215 (Oct 2, 2013)

  • 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

New in Datomic 0.8.4159 (Sep 12, 2013)

  • 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.

New in Datomic 0.8.4143 (Aug 22, 2013)

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

New in Datomic 0.8.4138 (Aug 19, 2013)

  • 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 in Datomic 0.8.4111 (Aug 1, 2013)

  • 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).

New in Datomic 0.8.4020.26 (Jul 10, 2013)

  • 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

New in Datomic 0.8.4020.24 (Jul 1, 2013)

  • 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.

New in Datomic 0.8.4020 (Jun 20, 2013)

  • 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.

New in Datomic 0.8.4007 (Jun 12, 2013)

  • 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

New in Datomic 0.8.3993 (Jun 4, 2013)

  • 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.

New in Datomic 0.8.3971 (Jun 4, 2013)

  • 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.

New in Datomic 0.8.3960 (May 21, 2013)

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

New in Datomic 0.8.3952 (May 16, 2013)

  • 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.

New in Datomic 0.8.3941 (May 11, 2013)

  • Excision

New in Datomic 0.8.3899 (May 9, 2013)

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

New in Datomic 0.8.3895 (Apr 26, 2013)

  • 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.

New in Datomic 0.8.3889 (Apr 15, 2013)

  • 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.

New in Datomic 0.8.3862 (Mar 30, 2013)

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

New in Datomic 0.8.3861 (Mar 28, 2013)

  • 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`

New in Datomic 0.8.3848 (Mar 14, 2013)

  • 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"

New in Datomic 0.8.3843 (Mar 12, 2013)

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

New in Datomic 0.8.3826 (Feb 26, 2013)

  • 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.

New in Datomic 0.8.3814 (Feb 14, 2013)

  • 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.
  • Renamed system property `datomic.objectCacheBytes` to datomic.objectCacheMax` for consistency with other property names.

New in Datomic 0.8.3803 (Feb 13, 2013)

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

New in Datomic 0.8.3789 (Feb 4, 2013)

  • 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.

New in Datomic 0.8.3784 (Feb 2, 2013)

  • 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
  • Overhauled the metrics reported by the transactor.
  • Fixed bug that caused incomplete garbage collection of storage on DynamoDB.

New in Datomic 0.8.3767 (Jan 24, 2013)

  • 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.

New in Datomic 0.8.3731 (Jan 11, 2013)

  • 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.

New in Datomic 0.8.3705 (Jan 9, 2013)

  • Upgrade to HornetQ 2.2.21.

New in Datomic 0.8.3704 (Jan 4, 2013)

  • 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.

New in Datomic 0.8.3692 (Dec 29, 2012)

  • 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.

New in Datomic 0.8.3664 (Dec 17, 2012)

  • 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.

New in Datomic 0.8.3655 (Dec 13, 2012)

  • 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.

New in Datomic 0.8.3646 (Dec 11, 2012)

  • 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.

New in Datomic 0.8.3627 (Nov 28, 2012)

  • 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.

New in Datomic 0.8.3619 (Nov 22, 2012)

  • 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 is now available from Maven
  • Central and clojars.

New in Datomic 0.8.3611 (Nov 21, 2012)

  • Peers now need to include the Datomic maven library in their repositories listing.
  • 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.

New in Datomic 0.8.3599 (Nov 9, 2012)

  • 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.

New in Datomic 0.8.3595 (Nov 5, 2012)

  • 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.

New in Datomic 0.8.3591 (Nov 2, 2012)

  • 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.

New in Datomic 0.8.3561 (Oct 24, 2012)

  • 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.

New in Datomic 0.8.3551 (Oct 11, 2012)

  • Fixes to alpha aggregation functions

New in Datomic 0.8.3546 (Oct 11, 2012)

  • Alpha support for aggregation functions in query.

New in Datomic 0.8.3538 (Sep 22, 2012)

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

New in Datomic 0.8.3524 (Sep 17, 2012)

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

New in Datomic 0.8.3520 (Sep 17, 2012)

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

New in Datomic 0.8.3511 (Sep 17, 2012)

  • 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.

New in Datomic 0.8.3488 (Sep 17, 2012)

  • Initial version of REST service.

New in Datomic 0.8.3479 (Sep 5, 2012)

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

New in Datomic 0.8.3470 (Aug 31, 2012)

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

New in Datomic 0.8.3460 (Aug 30, 2012)

  • 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.

New in Datomic 0.8.3438 (Aug 30, 2012)

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

New in Datomic 0.8.3435 (Aug 30, 2012)

  • 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 in Datomic 0.8.3423 (Aug 30, 2012)

  • 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

New in Datomic 0.8.3397 (Aug 30, 2012)

  • 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

New in Datomic 0.8.3372 (Aug 30, 2012)

  • 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

New in Datomic 0.8.3343 (Aug 30, 2012)

  • 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