Skip to content

docs: update 2026 roadmap#34194

Merged
guanshengliang merged 1 commit intomainfrom
docs/roadmap2026
Jan 7, 2026
Merged

docs: update 2026 roadmap#34194
guanshengliang merged 1 commit intomainfrom
docs/roadmap2026

Conversation

@guanshengliang
Copy link
Copy Markdown
Contributor

Description

Issue(s)

  • Close/close/Fix/fix/Resolve/resolve: Issue Link

Checklist

Please check the items in the checklist if applicable.

  • Is the user manual updated?
  • Are the test cases passed and automated?
  • Is there no significant decrease in test coverage?

@guanshengliang guanshengliang requested a review from zitsen as a code owner January 7, 2026 07:03
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @guanshengliang, 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 official product roadmap documentation for TDengine OSS. The primary goal is to reflect the strategic direction and planned features for the upcoming year, ensuring that users and stakeholders have access to the most current development plans. This change provides a clear outlook on the evolution of the product for 2026.

Highlights

  • Roadmap Update: The product roadmap documentation has been updated from the 2025 plan to the new 2026 plan for TDengine OSS.
  • Content Replacement: The detailed quarterly feature lists for 2025 (Q1-Q4) have been entirely replaced with the new strategic features planned for 2026 (Q1-Q4) in both English and Chinese documentation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@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

This pull request updates the product roadmap from 2025 to 2026 in both the English and Chinese documentation files. The changes are mostly content replacement. I've provided a couple of suggestions to improve formatting consistency and readability in both documents, such as wrapping technical keywords in backticks and ensuring consistent list formatting. Overall, the changes look good.

Comment on lines +9 to +12
| 2026Q1 | <ol><li>Storage: batch tag modification, dynamic adjustment of last cache LRU</li><li>Query: subqueries, external windows, ANY/SOME/ALL/EXISTS operators, window and interpolation enhancements, Explain and Show Queries optimization</li><li>Virtual Tables: virtual tables support referencing virtual tables, virtual table query performance optimization, subscription to virtual table metadata changes</li><li>Stream: triggering by natural week/month/quarter/year, event trigger condition optimization, grouped computation performance optimization, virtual supertable triggering supports child table additions/deletions/modifications</li></ol> |
| 2026Q2 | <ol><li>Storage: multi-replica leader switching and node recovery optimization, last cache optimization (such as forced refresh, multi-column write optimization, specified column caching)</li><li>Query: join queries, relaxed window query restrictions, time windows support week/month/quarter/year, Interp performance improvement</li><li>Functions: window functions and OVER clause</li><li>Virtual Tables: support for virtual table inheritance, virtual supertable column name modification</li><li>Stream: performance optimization for multiple customer scenarios, performance optimization for multi-measurement point scenarios, historical computation performance optimization, virtual table triggering performance optimization</li><li>Others: TDgpt predictive maintenance, minute-level timezone support</li></ol> |
| 2026Q3 | <ol><li>Query: complex query performance optimization, scalar correlated subqueries, cumulative windows, further enhancement of join queries, SQL testing tools</li><li>Functions: 15 customer-requested functions</li><li>Virtual Tables: subscription to virtual table data through continuous queries</li><li>Stream: maintainability improvement</li><li>Others: TDgpt supports PCA, PLS, cluster analysis</li></ol> |
| 2026Q4 | <ol><li>TEXT data type, variable-length string data type, database name modification, column name modification</li><li>Query: query parallelization, addition of observability metrics</li><li>Functions: support for MySQL operators and functions, UDF function framework refactoring</li><li>Others: engine CPU and memory management</li></ol> |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For better readability and consistency, it's good practice to format SQL keywords, commands, and function names as code using backticks. This helps distinguish them from regular text. I've applied this to terms like Explain, Interp, OVER, SQL, TEXT, and UDF.

Additionally, for consistency with other quarters and the Chinese version of this document, I've added the Storage: prefix to the first item in Q4, as it appears to describe storage-related features.

Suggested change
| 2026Q1 | <ol><li>Storage: batch tag modification, dynamic adjustment of last cache LRU</li><li>Query: subqueries, external windows, ANY/SOME/ALL/EXISTS operators, window and interpolation enhancements, Explain and Show Queries optimization</li><li>Virtual Tables: virtual tables support referencing virtual tables, virtual table query performance optimization, subscription to virtual table metadata changes</li><li>Stream: triggering by natural week/month/quarter/year, event trigger condition optimization, grouped computation performance optimization, virtual supertable triggering supports child table additions/deletions/modifications</li></ol> |
| 2026Q2 | <ol><li>Storage: multi-replica leader switching and node recovery optimization, last cache optimization (such as forced refresh, multi-column write optimization, specified column caching)</li><li>Query: join queries, relaxed window query restrictions, time windows support week/month/quarter/year, Interp performance improvement</li><li>Functions: window functions and OVER clause</li><li>Virtual Tables: support for virtual table inheritance, virtual supertable column name modification</li><li>Stream: performance optimization for multiple customer scenarios, performance optimization for multi-measurement point scenarios, historical computation performance optimization, virtual table triggering performance optimization</li><li>Others: TDgpt predictive maintenance, minute-level timezone support</li></ol> |
| 2026Q3 | <ol><li>Query: complex query performance optimization, scalar correlated subqueries, cumulative windows, further enhancement of join queries, SQL testing tools</li><li>Functions: 15 customer-requested functions</li><li>Virtual Tables: subscription to virtual table data through continuous queries</li><li>Stream: maintainability improvement</li><li>Others: TDgpt supports PCA, PLS, cluster analysis</li></ol> |
| 2026Q4 | <ol><li>TEXT data type, variable-length string data type, database name modification, column name modification</li><li>Query: query parallelization, addition of observability metrics</li><li>Functions: support for MySQL operators and functions, UDF function framework refactoring</li><li>Others: engine CPU and memory management</li></ol> |
| 2026Q1 | <ol><li>Storage: batch tag modification, dynamic adjustment of last cache LRU</li><li>Query: subqueries, external windows, ANY/SOME/ALL/EXISTS operators, window and interpolation enhancements, `Explain` and `Show Queries` optimization</li><li>Virtual Tables: virtual tables support referencing virtual tables, virtual table query performance optimization, subscription to virtual table metadata changes</li><li>Stream: triggering by natural week/month/quarter/year, event trigger condition optimization, grouped computation performance optimization, virtual supertable triggering supports child table additions/deletions/modifications</li></ol> |
| 2026Q2 | <ol><li>Storage: multi-replica leader switching and node recovery optimization, last cache optimization (such as forced refresh, multi-column write optimization, specified column caching)</li><li>Query: join queries, relaxed window query restrictions, time windows support week/month/quarter/year, `Interp` performance improvement</li><li>Functions: window functions and `OVER` clause</li><li>Virtual Tables: support for virtual table inheritance, virtual supertable column name modification</li><li>Stream: performance optimization for multiple customer scenarios, performance optimization for multi-measurement point scenarios, historical computation performance optimization, virtual table triggering performance optimization</li><li>Others: TDgpt predictive maintenance, minute-level timezone support</li></ol> |
| 2026Q3 | <ol><li>Query: complex query performance optimization, scalar correlated subqueries, cumulative windows, further enhancement of join queries, `SQL` testing tools</li><li>Functions: 15 customer-requested functions</li><li>Virtual Tables: subscription to virtual table data through continuous queries</li><li>Stream: maintainability improvement</li><li>Others: TDgpt supports PCA, PLS, cluster analysis</li></ol> |
| 2026Q4 | <ol><li>Storage: `TEXT` data type, variable-length string data type, database name modification, column name modification</li><li>Query: query parallelization, addition of observability metrics</li><li>Functions: support for MySQL operators and functions, `UDF` function framework refactoring</li><li>Others: engine CPU and memory management</li></ol> |

Comment on lines +9 to +12
| 2026Q1 | <ol><li>存储:批量标签修改、动态调整数据缓存的 LRU</li><li>查询:子查询、外部窗口、ANY/SOME/ALL/EXISTS 运算符、窗口及插值增强、Explain 和 Show Queries 优化</li><li>虚拟表:虚拟表支持引用虚拟表、虚拟表查询性能优化、订阅虚拟表的元数据变更</li><li>流计算:按自然周/月/季/年触发、事件触发条件优化、分组计算性能优化、虚拟超级表触发支持子表增删改</li></ol> |
| 2026Q2 | <ol><li>存储:多副本切主和节点恢复优化、数据缓存优化(如强制刷新、多列写入优化、指定列缓存)</li><li>查询:关联查询,放宽窗口查询限制、时间窗口支持周/月/季/年、Interp 性能提升</li><li>函数:窗口函数及 OVER 字句</li><li>虚拟表:支持虚拟表继承、虚拟超级表列名修改</li><li>流计算:多个客户场景性能优化、多测点场景性能优化、历史计算性能优化、虚拟表触发性能优化</li><li>其他:TDgpt 预测性维护、分钟级时区</li></ol> |
| 2026Q3 | <ol><li>查询:复杂查询性能优化、标量相关子查询、累计窗口、关联查询进一步增强、SQL 测试工具</li><li>函数:15 个客户需要的函数</li><li>虚拟表:通过连续查询订阅虚拟表数据</li><li>流计算:可维护性提升</li><li>其他:TDgpt 支持 PCA、PLS、聚类分析</li></ol> |
| 2026Q4 | <ol><li>存储:TEXT 数据类型、不定长字符串数据类型、库名修改、列名修改</li><li>查询:查询并行化、增加可观测指标</li><li>函数:支持 MySQL 运算符及函数、UDF 函数框架重构</li><li>其他:引擎的 CPU 和内存管控</li></ol> |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For better readability and consistency, it's good practice to format SQL keywords, commands, and function names as code using backticks. This helps distinguish them from regular text. I've applied this to terms like Explain, Interp, OVER, SQL, TEXT, and UDF.

Additionally, in the Q2 Query features list, I've changed the comma (,) after 关联查询 to an enumeration comma (、) to be consistent with the punctuation used in other lists in this document.

Suggested change
| 2026Q1 | <ol><li>存储:批量标签修改、动态调整数据缓存的 LRU</li><li>查询:子查询、外部窗口、ANY/SOME/ALL/EXISTS 运算符、窗口及插值增强、Explain 和 Show Queries 优化</li><li>虚拟表:虚拟表支持引用虚拟表、虚拟表查询性能优化、订阅虚拟表的元数据变更</li><li>流计算:按自然周/月/季/年触发、事件触发条件优化、分组计算性能优化、虚拟超级表触发支持子表增删改</li></ol> |
| 2026Q2 | <ol><li>存储:多副本切主和节点恢复优化、数据缓存优化(如强制刷新、多列写入优化、指定列缓存)</li><li>查询:关联查询放宽窗口查询限制、时间窗口支持周/月/季/年、Interp 性能提升</li><li>函数:窗口函数及 OVER 字句</li><li>虚拟表:支持虚拟表继承、虚拟超级表列名修改</li><li>流计算:多个客户场景性能优化、多测点场景性能优化、历史计算性能优化、虚拟表触发性能优化</li><li>其他:TDgpt 预测性维护、分钟级时区</li></ol> |
| 2026Q3 | <ol><li>查询:复杂查询性能优化、标量相关子查询、累计窗口、关联查询进一步增强、SQL 测试工具</li><li>函数:15 个客户需要的函数</li><li>虚拟表:通过连续查询订阅虚拟表数据</li><li>流计算:可维护性提升</li><li>其他:TDgpt 支持 PCA、PLS、聚类分析</li></ol> |
| 2026Q4 | <ol><li>存储:TEXT 数据类型、不定长字符串数据类型、库名修改、列名修改</li><li>查询:查询并行化、增加可观测指标</li><li>函数:支持 MySQL 运算符及函数、UDF 函数框架重构</li><li>其他:引擎的 CPU 和内存管控</li></ol> |
| 2026Q1 | <ol><li>存储:批量标签修改、动态调整数据缓存的 LRU</li><li>查询:子查询、外部窗口、ANY/SOME/ALL/EXISTS 运算符、窗口及插值增强、`Explain``Show Queries` 优化</li><li>虚拟表:虚拟表支持引用虚拟表、虚拟表查询性能优化、订阅虚拟表的元数据变更</li><li>流计算:按自然周/月/季/年触发、事件触发条件优化、分组计算性能优化、虚拟超级表触发支持子表增删改</li></ol> |
| 2026Q2 | <ol><li>存储:多副本切主和节点恢复优化、数据缓存优化(如强制刷新、多列写入优化、指定列缓存)</li><li>查询:关联查询放宽窗口查询限制、时间窗口支持周/月/季/年、`Interp` 性能提升</li><li>函数:窗口函数及 `OVER` 字句</li><li>虚拟表:支持虚拟表继承、虚拟超级表列名修改</li><li>流计算:多个客户场景性能优化、多测点场景性能优化、历史计算性能优化、虚拟表触发性能优化</li><li>其他:TDgpt 预测性维护、分钟级时区</li></ol> |
| 2026Q3 | <ol><li>查询:复杂查询性能优化、标量相关子查询、累计窗口、关联查询进一步增强、`SQL` 测试工具</li><li>函数:15 个客户需要的函数</li><li>虚拟表:通过连续查询订阅虚拟表数据</li><li>流计算:可维护性提升</li><li>其他:TDgpt 支持 PCA、PLS、聚类分析</li></ol> |
| 2026Q4 | <ol><li>存储:`TEXT` 数据类型、不定长字符串数据类型、库名修改、列名修改</li><li>查询:查询并行化、增加可观测指标</li><li>函数:支持 MySQL 运算符及函数、`UDF` 函数框架重构</li><li>其他:引擎的 CPU 和内存管控</li></ol> |

@guanshengliang guanshengliang merged commit 9c5eef9 into main Jan 7, 2026
9 checks passed
@minhuinie minhuinie deleted the docs/roadmap2026 branch February 4, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant