mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
8e31e8e6a8
* [Self-service error codes] Enabled by default * Flag changed to `use-pre-1.18-error-codes` (disabled by default) CHANGELOG_BEGIN [Ledger API Specification] The Ledger API returns enriched error codes (see https://docs.daml.com/error-codes/self-service/index.html) For backwards-compatibility, a new API flag `--use-pre-1.18-error-codes` is introduced for preserving the legacy behavior for clients that want to migrate incrementally to the changed gRPC status code responses and error details format. CHANGELOG_END * Adapted HttpServiceIntegrationTest * Renamed `Feature Flag` to `Configuration` in docs * Fix Daml Script tests changelog_begin changelog_end * Fix Repl functests changelog_begin changelog_end * Fix haskell binding tests changelog_begin changelog_end * Fix CommandClientIT test * Fixed Sandbox and CommandServiceBackpressureIT tests Please enter the commit message for your changes. Lines starting * Adapt //compiler/damlc/tests:repl-functests again * Fix more tests and address Miklos' comments * Flag name changed to `grpc-status-codes-compatibility-mode` * Remove useless flags sandbox-classic * Sandbox-classic tests fix for ContractKeysIT and ExceptionsIT * Created 2 deprecated test suites that have the more generic assertions as returned by the deprecated in-memory backend * More fixes for CommandServiceIT * Fixes compilation issue with the deprecated exceptionsIT class for Sandbox-classic in-memory * Compatibility mode for old test tools * Change flag name to `use-pre-1.18-error-codes` * Apply suggestions from code review Co-authored-by: Miklos <57664299+miklos-da@users.noreply.github.com> Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org> Co-authored-by: Miklos <57664299+miklos-da@users.noreply.github.com> |
||
---|---|---|
.. | ||
src | ||
BUILD.bazel | ||
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.