Ticket #187 (closed enhancement: fixed)

Opened 2 years ago

Last modified 1 year ago

Write a log of all Kowari transactions for recovery purposes

Reported by: ronald Assigned to: ronald
Priority: unassigned Milestone:
Component: topaz Version: 0.5-SNAPSHOT
Keywords: mulgara backup resolver Cc:
Blocking: Blocked By:

Description

In order to protect against data loss in the event of a database corruption, the filter-resolver will write all updates to a log file which can then be replayed.

Dependency Graph

Change History

10/02/06 21:43:12 changed by ronald

  • status changed from new to assigned.

10/04/06 03:21:22 changed by ronald

(In [736]) Addresses #187: introduced FilterHandler? interface to encapsulate the handler functionality and made FedoraUpdater? a FilterHandler?.

10/04/06 03:23:45 changed by ronald

(In [737]) Addresses #187: created transaction-logger which logs all model creations, deletions, and updates as iTQL commands in a log. The log is rotated when a configurable max-size or max-age is reached.

10/04/06 03:37:19 changed by ronald

(In [738]) Addresses #187: enable the filter-resolver in Kowari. The configured handler is the TransactionLogger?.

For historical purposes, the mods for the FedoraUpdater? are included too; these will be removed again in the next commit.

10/04/06 03:48:06 changed by ronald

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [739]) Removing legacy FedoraUpdater? config and deps from previous commit. Closes #187.

01/16/07 17:08:17 changed by ebrown

  • keywords changed from kowari backup resolver to mulgara backup resolver.

10/29/07 21:12:53 changed by

  • milestone deleted.

Milestone october16 deleted