diff --git a/roadmap.md b/roadmap.md index e311b85b932a0..d125b4ae13ee6 100644 --- a/roadmap.md +++ b/roadmap.md @@ -34,7 +34,7 @@ This roadmap brings you what's coming in the 1-year future, so you can see the n SQL - Support the JSON function. + Support the JSON function. In business scenarios that require flexible schema definitions, the application can use JSON to store information for ODS, transaction indicators, commodities, game characters, and props. @@ -42,7 +42,7 @@ This roadmap brings you what's coming in the 1-year future, so you can see the n 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. - Support time to live (TTL). + ✅ Support time to live (TTL). This feature enables automatic data cleanup in limited data archiving scenarios. @@ -50,7 +50,7 @@ This roadmap brings you what's coming in the 1-year future, so you can see the n Supports foreign key constraints compatible with MySQL syntax, and provides DB-level referential integrity check capabilities. - Support non-transactional DML for insert and update operations. + ✅ Support non-transactional DML for insert and update operations. @@ -59,7 +59,7 @@ This roadmap brings you what's coming in the 1-year future, so you can see the n Hybrid Transactional and Analytical Processing (HTAP) - Support TiFlash result write-back. + ✅ Support TiFlash result write-back.

Support INSERT INTO SELECT.

These features combined enable a way to materialize intermediate results. The analysis results can be easily reused, which reduces unnecessary ad-hoc queries, improves the performance of BI and other applications (by pulling results directly) and reduces system load (by avoiding duplicated computation), thereby improving the overall data pipeline efficiency and reducing costs. It will make TiFlash an online service.

@@ -124,12 +124,12 @@ This roadmap brings you what's coming in the 1-year future, so you can see the n Increase TiCDC's scalability by spanning data changes for single table to multiple TiCDC nodes and reduce replication latency by removing sorting stage. - Support replicating data to object storage such as S3. + ✅ Support replicating data to object storage such as S3. TiCDC supports replicating data changes to common object storage services. Data migration - Continuous data verification during data migration. + ✅ Continuous data verification during data migration. DM supports online data verification during migration from MySQL compatible database to TiDB. @@ -148,22 +148,22 @@ This roadmap brings you what's coming in the 1-year future, so you can see the n Password complexity check - A strong password is required. + ✅ A strong password is required. To improve security, empty passwords and weak passwords are not allowed.
The required password length is not less than 8. The password must contain an uppercase letter, a lowercase letter, a number, and a character. Password expiration - TiDB provides password expiration management and requires users to change passwords regularly. + ✅ TiDB provides password expiration management and requires users to change passwords regularly. Reduce the security risk of password cracking or leakage caused by using the same password for a long time. Password reuse policy - TiDB provides a password reuse policy. + ✅ TiDB provides a password reuse policy. Restrict password reuse and improve password security. Password anti-brute force cracking - Accounts will be locked in case of consecutive incorrect passwords. + ✅ Accounts will be locked in case of consecutive incorrect passwords. Lock the account under continuous wrong passwords to prevent the password from being cracked by brute force.