WIP: Add materialized views documentation

[windtalker]

What is changed, added or deleted? (Required)

Added a new Materialized Views overview page covering usage scenarios, prerequisites, create/manage flow, system tables, limitations, compatibility, and related links. Added reference pages for the user-queryable mysql.tidb_mview_refresh_hist, mysql.tidb_mview_refresh_alert, and mysql.tidb_mlog_purge_hist tables, and documented the internal refresh and purge scheduling tables in the overview. Added SQL syntax reference pages for CREATE MATERIALIZED VIEW, CREATE MATERIALIZED VIEW LOG, ALTER MATERIALIZED VIEW, ALTER MATERIALIZED VIEW LOG, DROP MATERIALIZED VIEW, and DROP MATERIALIZED VIEW LOG. Updated Views to remove the outdated note that materialized views are not supported and point readers to the new page.

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.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

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

• This PR is translated from: N/A
• Other reference link(s):
  • session, meta: add materialized view bootstrap system tables tidb#70599
  • parser: port materialized view DDL syntax tidb#70744
  • ddl: support create materialized view and log tidb#70789

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ti-chi-bot]

[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 lilin90 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.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[zhaoshangzi]

Syntax definations of materialized view are fine

[ti-chi-bot]

@zhaoshangzi: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Syntax definations of materialized view are fine

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.