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

Posted to issues@phoenix.apache.org by "Jacob Isaac (Jira)" <ji...@apache.org> on 2020/10/01 15:07:00 UTC

[jira] [Commented] (PHOENIX-5934) Design doc for PHOENIX TTL

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

Jacob Isaac commented on PHOENIX-5934:
--------------------------------------

[~kadir] [~larsh] [~gjacoby] [~ChinmayKulkarni] [~elserj] [~yanxinyi]

[~yanxinyi] Can u add the MR task design doc here too?

 

Linking it here for review and comments

> Design doc for PHOENIX TTL
> --------------------------
>
>                 Key: PHOENIX-5934
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5934
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Jacob Isaac
>            Assignee: Jacob Isaac
>            Priority: Major
>             Fix For: 4.16.0
>
>
> In the absence of TTL support on Phoenix entities, teams have to write custom application logic and use the Phoenix API to delete expired data in bulk. This proposal lays out a design to support TTL on Phoenix entities by masking expired rows during query time and providing a framework for deleting expired rows.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)