[
https://issues.apache.org/jira/browse/PHOENIX-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342166#comment-17342166
]
ASF GitHub Bot commented on PHOENIX-6457:
-----------------------------------------
gjacoby126 commented on pull request #1225:
URL: https://github.com/apache/phoenix/pull/1225#issuecomment-837430064
The initial 3 test failures from the first test run passed in the second. I
verified that AuditLoggingIT (failed in the second test run) passed locally, so
this appears to be a flapper. I also verified UpsertSelectIT from the initial
test failure locally and it passed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
