## Conclusion

+ Scenarios of TTL, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/>

+ Syntax of TTL, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/#syntax>

+ Job configuration of TTL, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/#ttl-job>

+ Observability of TTL, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/#observability>

+ Compatibility of TTL, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/#compatibility-with-sql>,<https://docs.pingcap.com/tidb/stable/time-to-live/#compatibility-with-tidb-tools>

+ Limitations of TTL, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/#limitations>

+ PCTA / PCTP Exam Knowledge Points:

  + TTL does not guarantee that all expired data is deleted immediately, which means that even if some data is expired, the client might still read that data some time after the expiration time until that data is deleted by the background TTL job, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/>.

  + How to set TTL attributes using generated columns, please refer to：<https://docs.pingcap.com/tidb/stable/time-to-live/#ttl-and-generated-columns>.

  + `tidb_ttl_job_enable` is used to control whether TTL jobs are enabled. If it is set to OFF, all tables with TTL attributes automatically stop cleaning up expired data. Please refer to：<https://docs.pingcap.com/tidb/stable/system-variables/#tidb_ttl_job_enable-new-in-v650>.
