Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Defaults to empty string, which is the full key range.
Apply should be continued from this key in reverse index.
Write id for first continued record.
Transaction commit hybrid time.
Transaction apply op id.
Set of aborted subtransactions.
History cutoff of all the tables of this tablet. On the master, this field is used for the sys catalog table. For cotables (i.e. ysql system tables) for which the cotables_history_cutoff field is used. On tservers, this field is used for everything i.e. both colocated and non colocated tables and the cotables_history_cutoff field is invalid.
Filter applies to all the entries of the sst file. Only set for the largest frontier.
Used only for sys catalog tablet during PITR restores to selectively restore some databases. Only set for the largest frontier.
Set only on the master for cotables.
Used in:
,A set of key/value pairs to be written into RocksDB.
Used in:
,Used by serializable isolation transactions and row locking statements to store read intents. In case of read-modify-write operation both read_pairs and write_pairs could present.
Even though there can be multiple write_pairs we have only one row_mark_type/ wait_policy since currently we don't batch read RPCs from YSQL (which are the only ones that can set these 2 fields). And hence, only a singular value is sufficient.
wait_policy is used only for explicit row-locking to identify 3 possibilities: WAIT_BLOCK, WAIT_SKIP, or WAIT_ERROR. See WaitPolicy for detailed information. If this request has read_pairs but row_mark_type is not set, then wait_policy should not be set. Such a situation can occur when read intents are to be written as part of SERIALIZABLE isolation level.
Table schema version used by this write batch. We could have writes to multiple cotables in a single write batch.
Advisory locks.
Used to prevent conflicts between session-level and transaction-level advisory locks within the same session. - For session-level advisory lock requests: background_transaction_id points to the in-progress DocDB transaction, if any. - For transaction-level advisory lock requests: background_transaction_id points to the session-level transaction, if exists.
Only relevant when the write op was launched for a session advisory lock request. Used by the wait-queue to resume deadlocked requests.
Used in:
lock or unlock.
This message is currently only being used for table level locks, which is protected under a test gflag that is disabled by default. The message shouldn't be re-used for production code.
Used in:
,Used in:
Used in:
,