This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch ignite-2.18
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/ignite-2.18 by this push:
new a8666c4cbc4 IGNITE-28688 Add missed transaction's system view
descriptions doc (#13146)
a8666c4cbc4 is described below
commit a8666c4cbc402b29187fdf4b3a15ca1f54ef3eab
Author: Didar Shayarov <[email protected]>
AuthorDate: Thu May 28 12:02:12 2026 +0300
IGNITE-28688 Add missed transaction's system view descriptions doc (#13146)
(cherry picked from commit d6ef99c448981dd03012a9903c306c04140496a2)
---
docs/_docs/SQL/sql-calcite.adoc | 2 +
docs/_docs/monitoring-metrics/system-views.adoc | 52 +++++++++++++------------
2 files changed, 29 insertions(+), 25 deletions(-)
diff --git a/docs/_docs/SQL/sql-calcite.adoc b/docs/_docs/SQL/sql-calcite.adoc
index b62ae85549d..6a1225c1754 100644
--- a/docs/_docs/SQL/sql-calcite.adoc
+++ b/docs/_docs/SQL/sql-calcite.adoc
@@ -955,6 +955,8 @@ The Calcite-based SQL engine currently supports the
following user-facing functi
|`TABLE(SYSTEM_RANGE(start, end[, increment]))`
|Returns a table with one `BIGINT` column named `X` and one row for each value
in the range.
+|===
+
=== Supported Data Types
Below are the data types supported by the Calcite-based SQL engine:
diff --git a/docs/_docs/monitoring-metrics/system-views.adoc
b/docs/_docs/monitoring-metrics/system-views.adoc
index fca31033d13..bc9c19dba90 100644
--- a/docs/_docs/monitoring-metrics/system-views.adoc
+++ b/docs/_docs/monitoring-metrics/system-views.adoc
@@ -267,34 +267,36 @@ methods. The parameter is empty, if you use
`IgniteCompute` APIs that don't targ
This view exposes information about currently running transactions.
+Each row in this view represents a transaction object on the node where the
view is queried. A distributed transaction can be represented by several
transaction objects on different nodes, such as near, DHT-local, and DHT-remote
transaction objects. Therefore, rows for the same distributed transaction can
differ from node to node.
+
[{table_opts}]
|===
|NAME | TYPE | DESCRIPTION
-|ORIGINATING_NODE_ID | UUID |
-|STATE | string |
-|XID | UUID |
-|LABEL | string |
-|START_TIME | long |
-|ISOLATION | string |
-|CONCURRENCY | string |
-|KEYS_COUNT | int |
-|CACHE_IDS | string |
-|COLOCATED | boolean |
-|DHT | boolean |
-|DURATION | long |
-|IMPLICIT | boolean |
-|IMPLICIT_SINGLE | boolean |
-|INTERNAL | boolean |
-|LOCAL | boolean |
-|LOCAL_NODE_ID | UUID |
-|NEAR | boolean |
-|ONE_PHASE_COMMIT | boolean |
-|OTHER_NODE_ID | UUID |
-|SUBJECT_ID | UUID |
-|SYSTEM | boolean |
-|THREAD_ID | long |
-|TIMEOUT | long |
-|TOP_VER | string |
+|ORIGINATING_NODE_ID | UUID | ID of the node that initiated the current
transaction object. For a transaction object mapped to a primary partition,
this is the transaction initiator node; for a transaction object mapped to a
backup partition, this is the node that owns the primary partition
+|STATE | string | Current transaction state
+|XID | UUID | Unique transaction identifier
+|LABEL | string | Transaction label
+|START_TIME | long | Start time of the transaction on this node
+|ISOLATION | string | Transaction isolation level
+|CONCURRENCY | string | Transaction concurrency mode
+|KEYS_COUNT | int | Number of cache keys participating in the transaction
+|CACHE_IDS | string | Comma-separated IDs of caches participating in the
transaction
+|COLOCATED | boolean | `True` if the transaction is DHT colocated
+|DHT | boolean | `True` if current node has data for this transaction
+|DURATION | long | Transaction duration in milliseconds
+|IMPLICIT | boolean | `True` if the transaction was started implicitly
+|IMPLICIT_SINGLE | boolean | `True` if the transaction is implicit with only
one key
+|INTERNAL | boolean | `True` if transaction operates with keys related to
Ignite internal data structures
+|LOCAL | boolean | `True` if this transaction object is on the initiator side
or mapped to a primary partition, `false` if it is mapped to a backup partition
+|LOCAL_NODE_ID | UUID | Local node ID
+|NEAR | boolean | `True` if the transaction is near
+|ONE_PHASE_COMMIT | boolean | `True` if the transaction is a one-phase-commit
transaction
+|OTHER_NODE_ID | UUID | ID of an additional node involved in the transaction
+|SUBJECT_ID | UUID | ID of the subject that initiated the transaction
+|SYSTEM | boolean | `True` if the transaction was started for a system cache
+|THREAD_ID | long | ID of the thread started the transaction
+|TIMEOUT | long | Transaction timeout in milliseconds
+|TOP_VER | string | Topology version assigned to the transaction. If not
assigned explicitly, it is a topology version of the latest partition exchange.
|===
== NODES
