Add command deduplication columns to completions in append-only schemas

CHANGELOG_BEGIN CHANGELOG_END
digital-asset · fabiotudone-da · Aug 31, 2021 · Aug 19, 2021 · Aug 23, 2021 · Aug 23, 2021
commit 8e54bb52b8f7f1f97b38799a45293fdea1d30306
diff --git a/...n-api/src/main/resources/db/migration/h2database-appendonly/V1__Append_only_schema.sha256 b/...n-api/src/main/resources/db/migration/h2database-appendonly/V1__Append_only_schema.sha256
@@ -1 +1 @@
-aae0b43e4735b3ffbdb782a61bad75f741c58a282327f3d3e18b0e41da5c69f6
+c9d6d032d1371e29bb84bf9e6dff92cb0dc162594c89c73a72786d2c41ec15cc
diff --git a/...tion-api/src/main/resources/db/migration/h2database-appendonly/V1__Append_only_schema.sql b/...tion-api/src/main/resources/db/migration/h2database-appendonly/V1__Append_only_schema.sql
@@ -122,6 +122,19 @@ CREATE TABLE participant_command_completions (
     command_id VARCHAR NOT NULL,
     -- The transaction ID is `NULL` for rejected transactions.
     transaction_id VARCHAR,
+    -- The application ID has to be provided by the application.
+    application_id VARCHAR NOT NULL,
+    -- The submission ID will be provided by the participant or driver if the application didn't provide one.
+    submission_id VARCHAR NOT NULL,
+    -- The three alternatives below are mutually exclusive, i.e. the deduplication
+    -- interval could have specified by the application as one of:
+    -- 1. an initial offset
+    -- 2. an initial timestamp
+    -- 3. a duration (split into two columns, seconds and nanos, mapping protobuf's 1:1)
+    deduplication_offset VARCHAR,
+    deduplication_start TIMESTAMP,
+    deduplication_time_seconds BIGINT,
+    deduplication_time_nanos INT,
     -- The three columns below are `NULL` if the completion is for an accepted transaction.
     -- The `rejection_status_details` column contains a Protocol-Buffers-serialized message of type
     -- `daml.platform.index.StatusDetails`, containing the code, message, and further details

diff --git a/...ation-api/src/main/resources/db/migration/oracle-appendonly/V1__Append_only_schema.sha256 b/...ation-api/src/main/resources/db/migration/oracle-appendonly/V1__Append_only_schema.sha256
@@ -1 +1 @@
-c9148396eec01471c1135ff384d0b83442442ada1d6ca12d731f8e84b6f4869f
+882dbf2fb1f48e5d240d21a5ba6bab7d60d6cc9306cbc0466ee9db4e0cf72458
diff --git a/...egration-api/src/main/resources/db/migration/oracle-appendonly/V1__Append_only_schema.sql b/...egration-api/src/main/resources/db/migration/oracle-appendonly/V1__Append_only_schema.sql
@@ -128,6 +128,19 @@ CREATE TABLE participant_command_completions
     record_time                 TIMESTAMP       NOT NULL,
 
     application_id              NVARCHAR2(1000) NOT NULL,
+    -- The submission ID will be provided by the participant or driver if the application didn't provide one.
+    submission_id               NVARCHAR2(1000) NOT NULL,
+
+    -- The three alternatives below are mutually exclusive, i.e. the deduplication
+    -- interval could have specified by the application as one of:
+    -- 1. an initial offset
+    -- 2. an initial timestamp
+    -- 3. a duration (split into two columns, seconds and nanos, mapping protobuf's 1:1)
+    deduplication_offset        VARCHAR2(4000),
+    deduplication_start         TIMESTAMP,
+    deduplication_time_seconds  NUMBER,
+    deduplication_time_nanos    NUMBER,
+
     submitters                  CLOB NOT NULL CONSTRAINT ensure_json_submitters CHECK (submitters IS JSON),
     command_id                  NVARCHAR2(1000) NOT NULL,
 

diff --git a/...ources/db/migration/postgres-appendonly/V108_add_deduplication_info_to_completions.sha256 b/...ources/db/migration/postgres-appendonly/V108_add_deduplication_info_to_completions.sha256
@@ -0,0 +1 @@
+6701a42bcb0229b873317f62e424297116bb79fcfbb3cb465076b81108dc6aac
diff --git a/...resources/db/migration/postgres-appendonly/V108_add_deduplication_info_to_completions.sql b/...resources/db/migration/postgres-appendonly/V108_add_deduplication_info_to_completions.sql
@@ -0,0 +1,19 @@
+--  Copyright (c) 2021 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
+--  SPDX-License-Identifier: Apache-2.0
+
+-- Add columns to store command deduplication information in completions.
+
+ALTER TABLE participant_command_completions
+    -- The application ID has to be provided by the application.
+    ADD COLUMN application_id text NOT NULL,
+    -- The submission ID will be provided by the participant or driver if the application didn't provide one.
+    ADD COLUMN submission_id text NOT NULL,
+    -- The three alternatives below are mutually exclusive, i.e. the deduplication
+    -- interval could have specified by the application as one of:
+    -- 1. an initial offset
+    -- 2. an initial timestamp
+    -- 3. a duration (split into two columns, seconds and nanos, mapping protobuf's 1:1)
+    ADD COLUMN deduplication_offset text,
+    ADD COLUMN deduplication_start timestamp,
+    ADD COLUMN deduplication_time_seconds bigint,
+    ADD COLUMN deduplication_time_nanos integer;
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		aae0b43e4735b3ffbdb782a61bad75f741c58a282327f3d3e18b0e41da5c69f6
		c9d6d032d1371e29bb84bf9e6dff92cb0dc162594c89c73a72786d2c41ec15cc
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		c9148396eec01471c1135ff384d0b83442442ada1d6ca12d731f8e84b6f4869f
		882dbf2fb1f48e5d240d21a5ba6bab7d60d6cc9306cbc0466ee9db4e0cf72458
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		6701a42bcb0229b873317f62e424297116bb79fcfbb3cb465076b81108dc6aac