[ https://issues.apache.org/jira/browse/PHOENIX-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacob Isaac reopened PHOENIX-5601: ---------------------------------- After discussion with [~kozdemir] [~larsh] and others, we arrived at the following decision # The client-side masking may not handle all use cases, for eg server-side scans # As the long term goal is to extend this to Phoenix Tables too, using a co-proc might be more efficient and may be easier to manage dependencies with other backend processes like backups, compaction ... More details in this design doc - PHOENIX-5934 > Add a new Coprocessor - ViewTTLAware Coprocessor > ------------------------------------------------ > > Key: PHOENIX-5601 > URL: https://issues.apache.org/jira/browse/PHOENIX-5601 > Project: Phoenix > Issue Type: Sub-task > Affects Versions: 5.1.0, 4.16.0 > Reporter: Jacob Isaac > Assignee: Jacob Isaac > Priority: Major > Attachments: PHOENIX-5601.4.x-HBase-1.3.008.patch, > PHOENIX-5601.master.008.patch > > > * Add a New coprocessor - ViewTTLAware Coprocessor that will intercept > scan/get requests to inject a new ViewTTLAware scanner. > The scanner will - > * Use the row timestamp of the empty column to determine whether row TTL > has expired and mask the rows from underlying query results. > * Use the row timestamp to delete expired rows when DELETE_VIEW_TTL_EXPIRED > flag is present. -- This message was sent by Atlassian Jira (v8.3.4#803005)