[
https://issues.apache.org/jira/browse/PHOENIX-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807843#comment-17807843
]
ASF GitHub Bot commented on PHOENIX-6996:
-----------------------------------------
lokiore commented on PR #1752:
URL: https://github.com/apache/phoenix/pull/1752#issuecomment-1896366340
> @lokiore - what happens if I don't want to upgrade HBase TTLs to Phoenix
TTLs at upgrade time, but I want to do it later?
@gjacoby126 No I added this only at upgrade time but after upgrade
phoenix.table.ttl.enabled if set true will expect that TTL defined in SYSCAT is
the TTL to follow, won't that break functionality if we don't do this at
upgrade time!?
I was expecting to know at upgrade time if we want older tables to follow
new TTL mechanism or not.
We can try to do this whenever we set phoenix.table.ttl.enabled to true and
check if this is done or not. But we would have to store the state.
> Provide an upgrade path for Phoenix tables with HBase TTL to move their TTL
> spec to SYSTEM.CATALOG
> --------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-6996
> URL: https://issues.apache.org/jira/browse/PHOENIX-6996
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Jacob Isaac
> Assignee: Lokesh Khurana
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
