Skip to content

include storage engines in slow query logs and statements summary #21155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

henrybw
Copy link

@henrybw henrybw commented Jun 12, 2025

First-time contributors' checklist

What is changed, added or deleted? (Required)

Document extra attributes added to identify the storage engine in both the statement summary and slow query log.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot bot added the first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. label Jun 12, 2025
Copy link

ti-chi-bot bot commented Jun 12, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign breezewish for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the missing-translation-status This PR does not have translation status info. label Jun 12, 2025
Copy link

pingcap-cla-assistant bot commented Jun 12, 2025

CLA assistant check
All committers have signed the CLA.

@ti-chi-bot ti-chi-bot bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 12, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @henrybw, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the documentation for TiDB's slow query log and statement summary features. It introduces descriptions for new fields that have been added to help users identify which storage engine (TiKV or TiFlash) was utilized when executing a query or a category of statements. This enhancement provides valuable context for performance analysis and debugging.

Highlights

  • Slow Query Log Documentation: Added documentation for new fields Storage_from_kv and Storage_from_mpp in the slow query log description. These fields indicate whether the statement read data from TiKV or TiFlash, respectively.
  • Statement Summary Documentation: Added documentation for new fields STORAGE_KV and STORAGE_MPP in the statement summary tables description. These fields indicate whether statements in that category read data from TiKV or TiFlash.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request successfully adds documentation for the new storage engine attributes in both the slow query logs and statement summary tables. The changes are well-formatted and adhere to the documentation style guide, enhancing the completeness and clarity of the relevant sections.

Comment on lines +171 to +174
Fields related to storage engines:

- `Storage_from_kv`: Whether this statement read data from TiKV.
- `Storage_from_mpp`: Whether this statement read data from TiFlash.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

This new section clearly documents the added fields related to storage engines. The formatting with a heading and list, using backticks for field names, aligns well with the style guide 12.

Style Guide References

Footnotes

  1. Use sentence case for headings and backticks for code snippets, command names, options, and paths. (link)

  2. Add a blank line before and after headings and lists. (link)

Comment on lines +470 to +473
Fields related to storage engines:

- `STORAGE_KV`: Indicates whether the previous execution of SQL statements of this category read data from TiKV.
- `STORAGE_MPP`: Indicates whether the previous execution of SQL statements of this category read data from TiFlash.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

This addition effectively documents the new storage engine fields in the statement summary tables. The structure with a heading and list, using backticks for field names, is consistent with the document's existing style and the style guide 12. The descriptions accurately reflect the purpose of these fields in the context of summary tables.

Style Guide References

Footnotes

  1. Use sentence case for headings and backticks for code snippets, command names, options, and paths. (link)

  2. Add a blank line before and after headings and lists. (link)

@Oreoxmt Oreoxmt added translation/doing This PR's assignee is translating this PR. v9.0-beta.2 This PR/issue applies to TiDB v9.0-beta.2. labels Jun 12, 2025
@ti-chi-bot ti-chi-bot bot removed the missing-translation-status This PR does not have translation status info. label Jun 12, 2025
@Oreoxmt Oreoxmt self-assigned this Jun 12, 2025
@Oreoxmt
Copy link
Collaborator

Oreoxmt commented Jun 13, 2025

@henrybw Could you please invite a tech reviewer? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
first-time-contributor Indicates that the PR was contributed by an external member and is a first-time contributor. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. translation/doing This PR's assignee is translating this PR. v9.0-beta.2 This PR/issue applies to TiDB v9.0-beta.2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants