Archive Service release notes

The Archive Service is a standalone service that operates on a different release cadence to the Corda platform.

The following table shows the compatibility of the Archive Service versions with Corda Enterprise:

Corda Enterprise 4.11 and above

Archive Service 1.1.1

Archive Service 1.1.1 is a patch release focused on resolving issues.

Fixed Issues

• When creating a backup table, the Archive Service created a backup table index name greater than 30 characters. This caused problems with Oracle 11.

• When used with a Corda 4.11 node, it was possible for the Archive Service create-snapshot command to fail. This issue occurred when the node database was one of SQL Server, Oracle, or PostgreSQL, and the Archive Service was configured to use a backup schema.

• When done immediately after a delete-vault operation, the import-snapshot failed to import transactions in an Archive Service regression.

Archive Service 1.1

In this release:

• Version 1.1 is a compatibility release of the Archive Service. This and all future 1.1.x releases will only work with Corda 4.11.x and above and will not be compatible with Corda Enterprise 4.10.x and below. Use the latest Archive Service 1.0.x for Corda Enterprise 4.10.x and below.
• In Corda Enterprise 4.11 a new column has been added to the node transactions table for additional signatures. The new Archive Service release includes this new column in its snapshot data.

Corda Enterprise 4.10 and below

Archive Service 1.0.6

Archive Service 1.0.6 is a patch release focused on resolving issues.

Fixed Issues

• When the node database was Oracle and the Archive Service was configured to use a backup schema, it was possible for the Archive Service create-snapshot command to fail.

• When creating a backup table, the Archive Service created a backup table index name greater than 30 characters. This caused problems with Oracle 11.

Archive Service 1.0.5

Fixed issues

The Archive Service misunderstood reference states. As a result, the Archive Service could not archive a transaction if it referenced an unconsumed transaction and there were no unconsumed transactions that referenced it.

As of this release, the Archive Service marks a transaction, that only has outbound references (to unconsumed transactions) and no inbound references (from unconsumed transactions), as archivable. Any inbound references will still make a transaction unarchivable.

Archive Service 1.0.4

Fixed issues

When using a Microsoft SQL Server database, an error was generated when using the vault-states filter with a positive value specified for the retentionDays parameter.

Archive Service 1.0.3

A new configuration option has been added which allows the Archive Service to skip transactions that have legacy contract states that cause exceptions during a JSON snapshot export. This configuration option is: ignoreSnapshotExportFailures: true.

By default, this value is false and the behaviour of the Archive Service is unchanged. However, if you are experiencing a TransactionDeserializationException or a JsonMappingException during the export of a JSON snapshot, this configuration option can be added to skip these transactions for a successful export. These transactions are not included in the export, but if a binary export is also created, all transactions can be preserved.

Archive Service 1.0.2

In this release:

• The archiving support of tokens when they are moved between more than one party and then redeemed has been improved.
• Logging of the Archiving tool has been increased to aid in troubleshooting.
• The Archiving client can now connect to nodes which are set up to use RPC SSL connection settings.
• Tables are now ordered by table name length in descending order to prevent foreign key constraints from being violated when deleting rows.

Archive Service 1.0.1

The Archive Service is now compatible with Ledger Graph V1.2.1 On Demand function.