<commit_before># TiDB Roadmap

This roadmap brings you what's coming in the 1-year future, so you can see the new features or improvements in advance, follow the progress, learn about the key milestones on the way, and give feedback as the development work goes on.

In the course of development, this roadmap is subject to change based on user needs and feedback. If you have a feature request or want to prioritize a feature, please file an issue on [GitHub](https://github.com/pingcap/tidb/issues).

## TiDB kernel

<table>
<thead>
  <tr>
    <th>Scenario</th>
    <th>Feature</th>
    <th>Description</th>
  </tr>
</thead>
<tbody>
  <tr>
    <td rowspan="2">Support JSON</td>
    <td>Support JSON function.</td>
    <td>In business scenarios that require flexible schema definitions (such as SaaS, Web3, and gaming), the application can use JSON to store information for ODS, transaction indicators, commodities, game characters, and props.</td>
  </tr>
  <tr>
    <td><ul><li>Support expression indexes.</li><li>Support generated columns.</li></ul></td>
    <td>Provide query acceleration for specific field indexes in JSON scenarios.</td>
  </tr>
  <tr>
    <td>Flashback</td>
    <td>Support cluster-level flashback.</td>
    <td>In game rollback scenarios, the flashback can be used to achieve a fast rollback of the current cluster. This solves the common problems in the gaming industry such as version errors and bugs.</td>
  </tr>
  <tr><commit_msg>docs: add disclaimer for roadmap (#38079)<commit_after># TiDB Roadmap

This roadmap brings you what's coming in the 1-year future, so you can see the new features or improvements in advance, follow the progress, learn about the key milestones on the way, and give feedback as the development work goes on. In the course of development, this roadmap is subject to change based on user needs and feedback. If you have a feature request or want to prioritize a feature, please file an issue on [GitHub](https://github.com/pingcap/tidb/issues).

> **Safe harbor statement:**
> 
> *Any unreleased features discussed or referenced in our documents, roadmaps, blogs, websites, press releases, or public statements that are not currently available ("unreleased features") are subject to change at our discretion and may not be delivered as planned or at all. Customers acknowledge that purchase decisions are solely based on features and functions that are currently available, and that PingCAP is not obliged to deliver aforementioned unreleased features as part of the contractual agreement unless otherwise stated.*

## TiDB kernel

<table>
<thead>
  <tr>
    <th>Scenario</th>
    <th>Feature</th>
    <th>Description</th>
  </tr>
</thead>
<tbody>
  <tr>
    <td rowspan="2">Support JSON</td>
    <td>Support JSON function.</td>
    <td>In business scenarios that require flexible schema definitions (such as SaaS, Web3, and gaming), the application can use JSON to store information for ODS, transaction indicators, commodities, game characters, and props.</td>
  </tr>
  <tr>
    <td><ul><li>Support expression indexes.</li><li>Support generated columns.</li></ul></td>
    <td>Provide query acceleration for specific field indexes in JSON scenarios.</td>
  </tr>
  <tr>
    <td>Flashback</td>
    <td>Support cluster-level flashback.</td>
    <td>In game rollback scenarios, the flashback can be used to achieve a fast rollback of the current cluster. This solves the common problems in the gaming industry such as version errors and bugs.</td>
  </tr>
  <tr>
{'fraction_non_alphanumeric': 0.09320829781187838, 'fraction_numerical': 0.00312588803637397, 'mean_word_length': 4.238095238095238, 'pattern_counts': {'":': 0, '<': 85, '<?xml version=': 0, '>': 88, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5670168', 'n_tokens_mistral': 981, 'n_tokens_neox': 939, 'n_words': 456}