hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16316) Prepare master branch for 3.0.0 development.
Date Mon, 10 Apr 2017 16:11:41 GMT

    [ https://issues.apache.org/jira/browse/HIVE-16316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963087#comment-15963087
] 

Naveen Gangam commented on HIVE-16316:
--------------------------------------

The 2 scenarios to consider are 
1) Hive 3.0 is released before Hive 2.3. Correct if if I am wrong, I think we are covered
in this case because the upgrade path would be 2.2.0 --> 3.0.0. We have all the scripts
in place for this upgrade.
2) Hive 3.0 is release after Hive 2.3. Where or not there are real schema changes between
2.3 and 3.0, there will always be a change to update the version in the VERSION table. So
when 2.3 is released, we will need to update the master to include scripts to upgrade from
2.3 to 3.0. The reason for deferring this change is 2-fold. a) there may never be a 2.3 release.
or b) Hive 2.4 or 2.5 might even be released before Hive 3.0 in which case we have to have
scripts for upgrade from the latest release.

Does this make sense? Thanks

> Prepare master branch for 3.0.0 development.
> --------------------------------------------
>
>                 Key: HIVE-16316
>                 URL: https://issues.apache.org/jira/browse/HIVE-16316
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 3.0.0
>            Reporter: Naveen Gangam
>            Assignee: Naveen Gangam
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16316.patch
>
>
> master branch is now being used for 3.0.0 development. The build files will need to reflect
this change.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message