---
title: "CDC Message Examples"
component: "tigergraph-server"
version: "3.11"
module: "system-management"
html_url: "/tigergraph-server/3.11/system-management/change-data-capture/cdc-message-example"
canonical_url: "https://www.tigergraph.com/docs/tigergraph-server/3.11/system-management/change-data-capture/cdc-message-example"
markdown_url: "https://www.tigergraph.com/docs/tigergraph-server/3.11/system-management/change-data-capture/cdc-message-example.md"
---

[View as HTML](https://www.tigergraph.com/docs/tigergraph-server/3.11/system-management/change-data-capture/cdc-message-example)

# CDC Message Examples

## Message Format Fields

### mid

`mid` is a message identifier field composed of concatenated elements, as exemplified by `2|1701548849757|33|2|1`. It is constructed by combining four or five elements, depending on its type, and each element is separated by `|`.

There are two types: **Non-transaction** and **Transaction**:

* **Non-transaction** types have 4 elements: `partitionID | timestamp | tid | index`
* **Transaction** types have 5 elements: `partitionID | timestamp | tid | split_index | index`

In the previous example, it signifies a **Transaction** with 5 elements: originating from partition `2|`, committed at epoch time `1701548849757|`, with transaction ID `33|`, split\_index of `2|`, and lastly an index of `1|`. The current message is the second message in the third batch of the transaction.

| "mid" Field Elements | Explain |
| --- | --- |
| `partitionID` | Source GPE partition of the CDC message. It starts from 1. |
| `timestamp` | Same as the timestamp field in the CDC message. |
| `tid` | A CDC message consistently corresponds to a delta message, both of which are part of a "delta batch" in the delta Kafka queue. The "tid" denotes the position or index of the delta batch to which the original delta message is mapped. This index starts from 1, and a transaction encompasses multiple delta batches. For CDC messages within a transaction, the "tid" corresponds to the "tid" of the last message, specifically the COMMIT message. |
| `split_index` | This element is exclusive to transactions. In the context of a transaction, the split\_index represents the position of the delta batch among all delta batches for the same transaction. It follows a 0-indexed format. |
| `index` | The index of the delta message in its delta batch. It's 0-indexed. |

### Other Message Fields

| Field | Value Type: "Possible Values" |
| --- | --- |
| `type` | String: "vertex" / "vertex-type" / "edge" |
| `operator` | String: "insert" / "insert-only" / "delete" |
| `timestamp` | UINT64: "**Non-transaction**: birth epoch time." / "**Transaction**: epoch time of transaction commit message." |
| `graph` \[in 3.11+\] | String: "GLOBAL", "<local\_graph\_name>" |
| `typename` | String: "type name of updated type". |
| `content` | See [Content Field Value Types and "Possible Values"](https://www.tigergraph.com/docs/tigergraph-server/3.11/system-management/change-data-capture/cdc-message-example.md#_content_field_value_types_and_possible_values) below. |

#### Content Field Value Types and "Possible Values"

* **Key** is the affected attribute name.
* **Value** is a JSON object with **2** fields:  
   1. "**op**": This defines how to apply the value to existing attribute value. It can be one of: `"Overwrite"`, `"Add"`, `"Max"`, `"Min"`, `"And"`, `"Or"`, `"IgnoreIfExisted"`, `"Minus"`, `"ReplaceOrAdd"`.  
   2. "**value**": As in this example below:  
   "content": {  
       "actors": {  
           "op": "Add",  
           "value": [  
               "i1",  
               "m2"  
           ]  
       },  
       ...  
   }

> [!NOTE]
> Content format change
> 
> Beginning with version 3.11, the format for the value of the `content` message field has been revised to be consistent with the [POST request data format](https://www.tigergraph.com/docs/tigergraph-server/3.11/API/index.md#_formatting_data_in_json). For example:
> 
> * Updated format: `{ "keylist":["k1", "k2"], "valuelist": [10.5, 24.8] }`
> * Legacy format: `{ "k1": 10.5, "k2": 24.8 }`
> 
> The legacy format is still available by setting `CDCLegacyFormat=true;` in `gadmin config entry GPE.BasicConfig.Env`.

## Message Examples

### CDC Message with Type: Vertex

This CDC message example indicates insertion, modification, or deletion of a vertex entity:

{
    "mid": "1|1701548849757|1|0",
    "operator": "insert",
    "timestamp": 1701548849757,
    "type": "vertex",
    "graph": "SocialGraph",
    "typename": "Company",
    "vid": 99999999,
    "uid": "comp1",
    "content": {
    "cid": {
        "op": "Overwrite",
        "value": 2345
    },
    "startDate": {
        "op": "Overwrite",
        "value": "2001-01-01 08:00:00"
        }
    }
}

#### Fields for CDC Message with Type: Vertex

| Field | Description |
| --- | --- |
| `vid` | Internal vertex id, eg: `1234567890`. |
| `uid` | External vertex id, eg: `"abc123"`. This could be `primary_id/primary key/composite keys`. And it will not appear in the content. |

#### Possible Operators for CDC Message with Type: Vertex

| "operator" | Note |
| --- | --- |
| `insert` | Insert a new vertex, or modify some attribute values |
| `insert-only` | Insert new vertex if not existing, otherwise ignore it. For now, this is only triggered in one case: when inserting an edge, the target vertex will be implicitly inserted with this "insert-only" operator. |
| `delete` | Delete a vertex will implicitly delete all edges that use that vertex as source or target. TigerGraph CDC service will **NOT** produce CDC messages for such "implicit edge deletion". |

### CDC Message with Type: Vertex-Type

This CDC message example indicates operations on all existing entities of a specific **vertex-type**:

{
    "mid": "1|1701548854014|2|0",
    "operator": "delete",
    "timestamp": 1701548854014,
    "type": "vertex-type",
    "graph": "SocialGraph",
    "typename": "Person",
    "content": {}
}

#### Possible operators for CDC Message with type vertex-type

| "operator" | Note |
| --- | --- |
| `delete` | Delete will delete all vertices of a vertex type and will also implicitly delete all edges that use that vertex as source or target. TigerGraph CDC service will **NOT** produce CDC messages for such "implicit edge deletion". |

### CDC Message with Type: Edge

This CDC message example indicate insertion, modification, or deletion of a edge entity:

{
    "mid": "1|1701569966031|3|0",
    "operator": "insert",
    "timestamp": 1701569966031,
    "type": "edge",
    "graph": "SocialGraph",
    "typename": "Creates",
    "hasreverseedge": true,
    "discriminator": "c1:1",
    "from": {
        "type": "Person",
        "vid": 12345678,
        "uid": "person2"
    },
    "to": {
        "type": "Company",
        "vid": 87654321,
        "uid": "comp2"
    },
    "content": {
        "attr_list_tuple": {
            "op": "Add",
            "value": [
                "i: 2, u: 0, f: 3, d: 3, dt: 1222819200, b: 0, s: m2"
            ]
        },
        "attr_map_tuple": {
            "op": "ReplaceOrAdd",
            "value": {
                "2011-10-20": "i: 2, u: 0, f: 3, d: 3, dt: 1222819200, b: 0, s: m2"
            }
        }
    }
}

#### Fields for CDC Message with Type: Edge

| Field | Optional? | Note |
| --- | --- | --- |
| `from` | No | JSON object with 3 fields:**type**: vertex type name of source vertex**vid**: internal vertex id of source vertex**uid**: external vertex id of source vertex. This could be `primary_id/primary key/composite` keys. For composite keys, the key is separated by a `,`. |
| `to` | No | Same as `from` field, but for target vertex. |
| `hasreverseedge` | Yes | Bool type. When the value is `true`, it means the updated edge type has also reverse edge types. If it's `false` this field will be omitted. |
| `discriminator` | Yes | String type. Only exists if the updated edge is multi-edge. It's the discriminator string separated by a `:`. |

#### Possible Operators for CDC Message with Type: Edge

| "operator" | Note |
| --- | --- |
| `insert` | Insert a new edge, or modified attribute values. If source vertex is missing when inserting edge, TigerGraph will implicitly insert source vertex with all default values on its attributes. For now, TigerGraph CDC Service will **NOT** produce CDC messages for such "implicit source vertex insertion". |
| `delete` | Deletion of an edge |

#### Extra CDC message for Edge Update

Edge updates may include additional information in specific scenarios.

In such cases, TigerGraph CDC will generate an additional CDC message for the corresponding "extra" edge.

| Case | Description |
| --- | --- |
| For directed edge without reverse edge type ("Simple Edge Type") | When a directed edge is inserted without a reverse edge type, TigerGraph automatically creates the source and/or target vertex if they do not exist. CDC messages are generated: \- For the source vertex: Only if it is new and has `primary_id_as_attribute="true"`. \- For the target vertex: Always if it is new. |
| For undirected edge, and directed edge with reverse edge type ("Complex Edge Type") | For insertion/modification/deletion on an undirected edge, or directed edge with a reverse edge type, TigerGraph will update 2 edges simultaneously: the "origin" edge and the "extra" edge with switched source and target vertex. When Undirected Edge or Directed Edge is inserted With a Reverse Edge Type, TigerGraph automatically creates the source and/or target vertex if they don't exist: \- **CDC messages** are generated for both source and target vertices only if they are new and have `primary_id_as_attribute="true"`. |
