Skip to content

Commit a8666c4

Browse files
w3ll1ngtalex-plekhanov
authored andcommitted
IGNITE-28688 Add missed transaction's system view descriptions doc (#13146)
(cherry picked from commit d6ef99c)
1 parent ddbb4f7 commit a8666c4

2 files changed

Lines changed: 29 additions & 25 deletions

File tree

docs/_docs/SQL/sql-calcite.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -955,6 +955,8 @@ The Calcite-based SQL engine currently supports the following user-facing functi
955955
|`TABLE(SYSTEM_RANGE(start, end[, increment]))`
956956
|Returns a table with one `BIGINT` column named `X` and one row for each value in the range.
957957

958+
|===
959+
958960
=== Supported Data Types
959961

960962
Below are the data types supported by the Calcite-based SQL engine:

docs/_docs/monitoring-metrics/system-views.adoc

Lines changed: 27 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -267,34 +267,36 @@ methods. The parameter is empty, if you use `IgniteCompute` APIs that don't targ
267267

268268
This view exposes information about currently running transactions.
269269

270+
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.
271+
270272
[{table_opts}]
271273
|===
272274
|NAME | TYPE | DESCRIPTION
273-
|ORIGINATING_NODE_ID | UUID |
274-
|STATE | string |
275-
|XID | UUID |
276-
|LABEL | string |
277-
|START_TIME | long |
278-
|ISOLATION | string |
279-
|CONCURRENCY | string |
280-
|KEYS_COUNT | int |
281-
|CACHE_IDS | string |
282-
|COLOCATED | boolean |
283-
|DHT | boolean |
284-
|DURATION | long |
285-
|IMPLICIT | boolean |
286-
|IMPLICIT_SINGLE | boolean |
287-
|INTERNAL | boolean |
288-
|LOCAL | boolean |
289-
|LOCAL_NODE_ID | UUID |
290-
|NEAR | boolean |
291-
|ONE_PHASE_COMMIT | boolean |
292-
|OTHER_NODE_ID | UUID |
293-
|SUBJECT_ID | UUID |
294-
|SYSTEM | boolean |
295-
|THREAD_ID | long |
296-
|TIMEOUT | long |
297-
|TOP_VER | string |
275+
|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
276+
|STATE | string | Current transaction state
277+
|XID | UUID | Unique transaction identifier
278+
|LABEL | string | Transaction label
279+
|START_TIME | long | Start time of the transaction on this node
280+
|ISOLATION | string | Transaction isolation level
281+
|CONCURRENCY | string | Transaction concurrency mode
282+
|KEYS_COUNT | int | Number of cache keys participating in the transaction
283+
|CACHE_IDS | string | Comma-separated IDs of caches participating in the transaction
284+
|COLOCATED | boolean | `True` if the transaction is DHT colocated
285+
|DHT | boolean | `True` if current node has data for this transaction
286+
|DURATION | long | Transaction duration in milliseconds
287+
|IMPLICIT | boolean | `True` if the transaction was started implicitly
288+
|IMPLICIT_SINGLE | boolean | `True` if the transaction is implicit with only one key
289+
|INTERNAL | boolean | `True` if transaction operates with keys related to Ignite internal data structures
290+
|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
291+
|LOCAL_NODE_ID | UUID | Local node ID
292+
|NEAR | boolean | `True` if the transaction is near
293+
|ONE_PHASE_COMMIT | boolean | `True` if the transaction is a one-phase-commit transaction
294+
|OTHER_NODE_ID | UUID | ID of an additional node involved in the transaction
295+
|SUBJECT_ID | UUID | ID of the subject that initiated the transaction
296+
|SYSTEM | boolean | `True` if the transaction was started for a system cache
297+
|THREAD_ID | long | ID of the thread started the transaction
298+
|TIMEOUT | long | Transaction timeout in milliseconds
299+
|TOP_VER | string | Topology version assigned to the transaction. If not assigned explicitly, it is a topology version of the latest partition exchange.
298300
|===
299301

300302
== NODES

0 commit comments

Comments
 (0)