phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-6457) Optionally store schema version string in SYSTEM.CATALOG
Date Tue, 11 May 2021 17:38:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Geoffrey Jacoby resolved PHOENIX-6457.
--------------------------------------
    Release Note: Introduces SCHEMA_VERSION property which can be updated during a CREATE
or ALTER statement with a string value that gives a user-understood version tag. 
      Resolution: Fixed

Merged to 4.x and master. Thanks for the reviews, [~gokcen] and [~swaroopa]

> Optionally store schema version string in SYSTEM.CATALOG
> --------------------------------------------------------
>
>                 Key: PHOENIX-6457
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6457
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>             Fix For: 4.17.0, 5.2.0
>
>
> In many environments, schema changes to Phoenix tables are applied in batches associated
with a version of an application. (For example, v1.0 of an app may start with one set of CREATE
statements, v1.1 then adds some ALTER statements, etc.) 
> It can be useful to be able to look up the latest app version in which a table or view
was changed; this could potentially be added as a feature of the Schema Tool. 
> This change would add an optional property to CREATE and ALTER statements, SCHEMA_VERSION,
which would take a user-supplied string. 
> This is also a pre-req for PHOENIX-6227, because we would want to pass the schema version
string, if any, to an external schema repository in environments where we're integrating with
one. 



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

Mime
View raw message