mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 17:28:46 +03:00

History

tudor-da 96ad9b5ab8 [Divulgence pruning] All divulgence events pruning [DPP-483] (#10634 ) * All divulgence events pruning * Add `pruneAllDivulgedContracts` to `IndexParticipantPruningService` * Add `participant_pruned_all_contracts_up_to_inclusive` in `parameters` table * `pruneEvents` prunes all divulgence events * Adapt `ParticipantPruningIT` to check for divulgence with and without `pruna_all_divulged_contracts` * Create multi-participant pruning test in ledger-on-memory CHANGELOG_BEGIN CHANGELOG_END * CommonStorageBackend * Enrich pruning descriptions * Logging for command completions pruning * Move divulgence pruning back to the beginning of pruning sequence * Addressed review comments * PRDivulgenceArchivalPruning adapted for privacy-aware ledgers * Rebased to main * Disable ParticipantPruningIT tests targeting append-only schema in mutable schema conformance tests in ledger-on-sql * Adapted order of SQL migration queries * Documentation of appendonlydao.JdbcLedgerDao.prune * Apply suggestions from code review Co-authored-by: Simon Meier <meiersi-da@users.noreply.github.com> Co-authored-by: Simon Meier <meiersi-da@users.noreply.github.com>		2021-08-26 08:45:01 +00:00
..
src	participant-integration-api: Always wait for the first config lookup. (#10500 )	2021-08-06 12:47:31 +00:00
BUILD.bazel	[Divulgence pruning] All divulgence events pruning [DPP-483] (#10634 )	2021-08-26 08:45:01 +00:00
README.md	Delete the Docker image targets. (#7932 )	2020-11-11 07:40:06 +00:00

README.md

Overview

This document is to help internal engineers work with ledger-on-memory.

ledger-on-memory is a key/value-based ledger that uses a simple in-memory map as an underlying storage. It uses either H2 or PostgreSQL as its index database.

Ledger On Memory

To build a fat JAR with the server built from HEAD run

bazel build //ledger/ledger-on-memory:app_deploy.jar

The application can be run from command line with the following command:

java -Xmx4G -XX:+UseG1GC -jar bazel-bin/ledger/ledger-on-memory/app_deploy.jar --participant participant-id=foo,port=6861

As run from the main project root directory (adjust the location of the JAR according to your working directory).

Alternatively, the application can be run using the Bazel command:

bazel run //ledger/ledger-on-memory:app -- --participant participant-id=foo,port=6861

Creating ledger exports

Ledger On Memory can be used to generate ledger exports through an environment variable:

export KVUTILS_LEDGER_EXPORT=/path/to/export/file

Then launch the ledger using the Bazel or Java command as described above.