TsukiokaKogane opened a new issue, #61056:
URL: https://github.com/apache/doris/issues/61056

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Description
   
   Currently, Apache Doris relies exclusively on dynamic partitions for data 
lifecycle management on aggregate model tables. Row-level TTL can help to 
improve query performance and reduce storage consumption. 
    <img width="1280" height="883" alt="Image" 
src="https://github.com/user-attachments/assets/9fa9b320-dc12-46d4-bf95-cf086bb61d29";
 />
   
   ### Use case
   
   Row-level TTL targets scenarios that require data expiration based on 
non-partition columns. It is applicable to date-range partitioned tables, LIST 
partitioned tables, and non-partitioned tables. Row-level TTL can work either 
with or without when Dynamic Partitioning is enabled.
   
   Use Case:
   ```sql
   CREATE TABLE example_db.example_tbl
   (
       k1 DATE,
       k2 INT,
       k3 SMALLINT,
       v1 VARCHAR(2048),
       v2 DATETIME DEFAULT "2014-02-04 15:36:00"
   )
   PARTITION BY RANGE (k1) ()
   DISTRIBUTED BY HASH(k2) BUCKETS 32
   PROPERTIES(
       "function_column.ttl_col" = "v2",
       "function_column.ttl" = "3d"
    );
   ```
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to