pingcap/tidb

Provide a session variable to query the last transaction scope

Open

#20,775 opened on Nov 2, 2020

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Go (6,186 forks)batch import
good first issuesig/transactiontype/enhancement

Repository metrics

Stars
 (40,090 stars)
PR merge metrics
 (PR metrics pending)

Description

Development Task

To figure out which transaction scope the last transaction uses, we need a read-only session variable to query it. This is a part of the global/local transaction roadmap #20448.

Implementations

It's similar to other session variables like last_insert_id and last_plan_from_cache. You can refer to the implementation of these variables.

Contributor guide

Research direction
Examine the implementation of session variables like `last insert id` and `last plan from cache` and create a new session variable for last transaction scope by following the same pattern.
Tech stack
go
Domain
backenddatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65