July 2025 monthly summary for pingcap/tidb. Focused on correctness and stability of the table analysis flow when handling vector columns. Implemented a bug fix to ensure vector columns are properly included in the skipCol list by the plan builder during analyze, and extended tests to cover a vector column and a generated virtual column based on it. The change tightens the planner/analyze integration and improves analysis accuracy for vector-based schemas.

Month 2025-04 – Tidb-engine-ext: Internal stability and security hardening completed with two targeted fixes. No user-facing features released this month; focus was on cross-platform build reliability and risk mitigation to maintain productivity and downstream compatibility.

February 2025: Documentation-only delivery in qiancai/docs-cn for TiDB CREATE TABLE ENGINE_ATTRIBUTE, clarifying behavior and future-use status to improve accuracy and reduce confusion.

Summary for 2025-01 (pingcap/tidb): Focused feature work delivering foundational support for engine-specific configuration via Engine Attribute in the Parser and DDL layers. This work lays the groundwork for future extensibility, enabling engine_attribute option handling and future attribute-driven configurations. Key achievements (top 4): - Engine Attribute support added to Parser and DDL to enable engine_attribute option (commit d0d48767b0a96bfb65513434e61913748aaa24ed). - Data structures and parsing logic updated to accommodate engine attribute codes and values for future extensibility. - Foundation established for engine-specific configurations across engines, aligning with long-term roadmap. - Clear commit-level traceability and reviewability for the feature change.