[
https://issues.apache.org/jira/browse/SENTRY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613690#comment-16613690
]
Hadoop QA commented on SENTRY-2398:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12939432/SENTRY-2398.3.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/4102/console
This message is automatically generated.
> Support multiple target versions on single source versions during schema
> upgrades
> ---------------------------------------------------------------------------------
>
> Key: SENTRY-2398
> URL: https://issues.apache.org/jira/browse/SENTRY-2398
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Priority: Major
> Attachments: SENTRY-2398.1.patch, SENTRY-2398.2.patch,
> SENTRY-2398.3.patch
>
>
> Currently, the SentrySchemaTool allows only upgrade versions that are in the
> order found in the upgrade.order.<db> files. However, having multiple direct
> target versions per source version is desired when dealing with complex
> scenarios where the upgrade path is not in the order of the file.
> For example:
> 1.8.0 -> 1.9.0
> 1.8.0 -> 2.0.0
> 1.9.0 -> 2.1.0
> 2.0.0 -> 2.1.0
>
> The above scenario mentions that 1.8.0 is allowed to be upgraded to 1.9.0 or
> 2.0.0, but 1.9.0 cannot upgrade to 2.0.0. Also, the 1.8.0 -> 2.0.0 was
> created before a 1.9.0 version is released.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
