[
https://issues.apache.org/jira/browse/HIVE-19323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489833#comment-16489833
]
Alan Gates commented on HIVE-19323:
-----------------------------------
The decision to run 3 simultaneous release lines (3.0.1, 3.1.0, and 4.0) has an
unfortunate side effect here. We will need multiple copies of the install and
upgrade scripts. And we have to answer what upgrades do we support from where?
Traditionally we have been linear in our upgrades which has been nice. But
that gets harder with multiple lines running. I propose the following:
# For now we don't create 3.0.1 install/upgrade scripts in the hope that bug
fixes won't include changes to the database. If we get unlucky and need them
we can add them later.
# We create 3.1 install and upgrade scripts.
# We create 4 install scripts and 3.1->4 upgrade. But, assuming we release
3.1, 3.2, etc. before 4, we move these upgrade scripts so that only 3.max->4 is
supported rather than 3.all->4. For example, assume the last 3 release is 3.3.
There would be 3.3->4.0 upgrade, but no 3.1 or 3.2 to 4. This is a little
weird because we'll be renaming these upgrade files when we do releases on 3
line. But it preserves the linearity of our upgrades and it works with our
existing tools.
Thoughts?
> Create metastore SQL install and upgrade scripts for 3.1
> --------------------------------------------------------
>
> Key: HIVE-19323
> URL: https://issues.apache.org/jira/browse/HIVE-19323
> Project: Hive
> Issue Type: Task
> Components: Metastore
> Affects Versions: 3.1.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Priority: Major
> Attachments: HIVE-19323.2.patch, HIVE-19323.3.patch, HIVE-19323.patch
>
>
> Now that we've branched for 3.0 we need to create SQL install and upgrade
> scripts for 3.1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
