[
https://issues.apache.org/jira/browse/PHOENIX-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994990#comment-16994990
]
Geoffrey Jacoby commented on PHOENIX-5613:
------------------------------------------
[~larsh] [~ckulkarni][~jisaac] - happy to hear counterarguments, but I'm pretty
sure I disagree.
We shouldn't be adding schema changes to system catalog to support a feature
that doesn't exist yet. The current plan might be to get view ttl in quickly in
a 4.15.1 or .2, but priorities and people change, and there's no guarantee that
it will happen as quickly as you expect. (For example, I was working on change
data capture during the summer, but had to shift back to helping out with
secondary indexes in the fall.)
In particular, we shouldn't be adding new-*anything* to 4.15 that isn't a bug
fix or a low-risk refactor, given how large the release already is.
Version numbers are free. If we need to cut a 4.16 in February for view ttl, we
can cut a 4.16 in February. (This also means that if some late-breaking
implementation detail of view ttl turns out to need a slightly different syscat
schema, Jacob has the freedom to make that change.)
Narrower, more frequent releases will make quality control and testing easier.
And if that means that some operators internally go straight from 4.14 to 4.16
rather than 4.15, that shouldn't be a problem.
> Add columns to SYSCAT to support TTL feature for views
> ------------------------------------------------------
>
> Key: PHOENIX-5613
> URL: https://issues.apache.org/jira/browse/PHOENIX-5613
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 4.15.0
> Reporter: Jacob Isaac
> Assignee: Jacob Isaac
> Priority: Major
> Fix For: 4.15.0
>
>
> Add columns VIEW_TTL, VIEW_TTL_HWM to hold TTL metadata for views in SYSCAT.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
