You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2022/10/28 03:11:00 UTC

[jira] [Comment Edited] (HUDI-1741) Row Level TTL Support for records stored in Hudi

    [ https://issues.apache.org/jira/browse/HUDI-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625400#comment-17625400 ] 

Nicholas Jiang edited comment on HUDI-1741 at 10/28/22 3:10 AM:
----------------------------------------------------------------

[~shivnarayan], IMO, each record of hudi has the commit time of hudi. The solution is to first follow the TTL, do not display expired data when checking, or even push down to the data source directly, and then delete it when doing operations such as clustering that need to rewrite the data. WDYT?

cc [~xleesf] 


was (Author: nicholasjiang):
[~shivnarayan], IMO, each record of hudi has the commit time of hudi. The solution is to first follow the TTL, do not display expired data when checking, or even push down to the data source directly, and then delete it when doing operations such as clustering that need to rewrite the data. WDYT?

> Row Level TTL Support for records stored in Hudi
> ------------------------------------------------
>
>                 Key: HUDI-1741
>                 URL: https://issues.apache.org/jira/browse/HUDI-1741
>             Project: Apache Hudi
>          Issue Type: New Feature
>          Components: Utilities
>            Reporter: Balaji Varadarajan
>            Priority: Major
>
> For e:g : Have records only updated last month 
>  
> GH: https://github.com/apache/hudi/issues/2743



--
This message was sent by Atlassian Jira
(v8.20.10#820010)