Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78636101E0 for ; Wed, 10 Dec 2014 22:57:13 +0000 (UTC) Received: (qmail 58544 invoked by uid 500); 10 Dec 2014 22:57:13 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 58479 invoked by uid 500); 10 Dec 2014 22:57:12 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 58467 invoked by uid 500); 10 Dec 2014 22:57:12 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 58464 invoked by uid 99); 10 Dec 2014 22:57:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 22:57:12 +0000 Date: Wed, 10 Dec 2014 22:57:12 +0000 (UTC) From: "Sushanth Sowmyan (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-9057) port HIVE-8295 to 0.13.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-9057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241894#comment-14241894 ] Sushanth Sowmyan commented on HIVE-9057: ---------------------------------------- The community decides if there's a 0.13.2. If there is enough need for a 0.13.2, and someone ( maybe you? :D ) wants to drive that, then we vote on it, and go through the process. For 0.13.1, soon after 0.13.0 was released, we hit several important bugs/breakages including a CVE that made 0.13.0 essentially unusable for some usage patterns. We fixed them in 0.14 trunk, but since it would be quite some time before a new stable hive release was released, we needed to make sure that the latest stable release of hive had those bugs fixed - this was what made 0.13.1 necessary. That bar of need, of having this bug fixed in this branch so that the latest stable hive has this fix, imo, does not exist for a 0.13.2 for this bug, since 0.14 is already out. That bar of need probably exists for 0.14.1, but you already have this checked in there. To that end, for 0.13.1, I proposed that we have a 0.13.1 as a bugfix release in the hive dev list, volunteered to be the RM for it, got a bunch of +1s, and then proceeded to roll it out. If you think that this deserves a new release, then I would invite you to suggest to the hive dev list that a 0.13.2 be rolled out, and proceed with the same process I followed for 0.13.1. If we were going through that process though, there might be a good point for a wholesale backport of a number of other bugfixes on 0.14.x to 0.13.2 as well, if there were enough people that wanted to upgrade from 0.13.1 to 0.13.2 instead of upgrading to 0.14.1. > port HIVE-8295 to 0.13.1 > ------------------------ > > Key: HIVE-9057 > URL: https://issues.apache.org/jira/browse/HIVE-9057 > Project: Hive > Issue Type: Bug > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Fix For: 0.13.1 > > Attachments: HIVE-9057.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)