Re: Preparation for Hive-1.2 release

Thank you all for your requests for inclusion over at https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status . This list is now frozen for any new requests for inclusion of ordinary bugfixes or features, and we'll work our way through RCs attempting to get all the outstanding issu

Re: Preparation for Hive-1.2 release

Hi Folks, As of yesterday, we had a dummy RC0 ready, and the time draws near to start getting all the issues set about in https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status to getting them resolved, and then rolling out an RC1. To do this, we must first freeze the list over t

Re: Preparation for Hive-1.2 release

Hi Folks, As per the timeline set on https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status , the time for requests for inclusion of any new features to branch-1.2 is now closed. Any JIRAS already marked in the lists previously will be honoured and considered release blockers, bu

Re: Preparation for Hive-1.2 release

HIVE-10509 and HIVE-10510 have been created with the individual patches that upgraded master and branch-1.2 respectively, and marked as resolved. I'll also add it in to the HowToRelease doc to ensure that from the next release onward, we create a jira for this. Also, friendly reminder for folks :

Re: Preparation for Hive-1.2 release

Also, Agreed with Sergio/Szehon, we should have a jira that's marked as committed with a patch attached for the version bump patch. Creating one. On Mon, Apr 27, 2015 at 4:39 PM, Sushanth Sowmyan wrote: > Vinod, > > If 2.7.0 is "not-yet-ready", then we should not be bumping 1.2 to > 2.7.0. But, w

Re: Preparation for Hive-1.2 release

Vinod, If 2.7.0 is "not-yet-ready", then we should not be bumping 1.2 to 2.7.0. But, we should be okay to bump master(1.3) up to 2.7.0 so that we start general-purpose testing against that. Please go ahead and create a jira for that, and we should be able to bump up trunk to go against that. Tha

Re: Preparation for Hive-1.2 release

Hi, Coming from the Apache Hadoop community. We made a recent release of 2.7.0 [1]. We are calling it not-yet-ready with one of the primary intentions to get it vetted through downstream projects. We plan to release a 2.7.1 (or 2.7.2) when it is considered stable enough for most of our users.

Re: Preparation for Hive-1.2 release

Hi, Sergio is mentioning the actual commit to move to 1.3 version: https://github.com/apache/hive/commit/123bb8e1a466f46fa54855b15961c274846a3b31, which touches the metastore scripts. Such commits should have a JIRA and patch attached, in order to run the metastore upgrade pre-commit tests and ma

Re: Preparation for Hive-1.2 release

Created 1.3.0 version in jira. As Sushanth mentioned, please use this fix version for changes being committed to trunk only. On Sat, Apr 25, 2015 at 2:53 AM, Sushanth Sowmyan wrote: > Hi Folks, > > branch-1.2 is now created, and master has been bumped to 1.3.0-SNAPSHOT. > > Carl/Thejas, I do not

Re: Preparation for Hive-1.2 release

Hi, I notice that the process of creating a new version does not involve a JIRA ticket where we track a patch for changes committed to master. One of the tests that was recently created on Jenkins is a job that run all HMS upgrade tests for mysql/postgres/derby (oracle is still in progress) when

Re: Preparation for Hive-1.2 release

Hi Folks, branch-1.2 is now created, and master has been bumped to 1.3.0-SNAPSHOT. Carl/Thejas, I do not have permissions to create a new unreleased version number for 1.3.0 on jira - could one of you please create this so any new resolved jiras can be marked with this instead? Everyone else : O

Re: Preparation for Hive-1.2 release

Thanks, Szehon! Next week should be good. On Fri, Apr 24, 2015 at 2:17 PM, Szehon Ho wrote: >> >> Szehon, once we have a separate branch, would it be okay to set up a >> nightly test run on that branch? > > > Yea should be ok, one of us could look at that next week. > > Thanks > Szehon > > On Fri

Re: Preparation for Hive-1.2 release

> > Szehon, once we have a separate branch, would it be okay to set up a > nightly test run on that branch? Yea should be ok, one of us could look at that next week. Thanks Szehon On Fri, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan wrote: > Hi All, > > I'd like to send along a last reminder peo

Re: Preparation for Hive-1.2 release

Hi All, I'd like to send along a last reminder people to add any jiras that people want included in 1.2 to https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status or reply to this mail with any further requests for inclusions. As it currently stands, even though we did have a cou

Re: Preparation for Hive-1.2 release

The Apache Accumulo project has written a nice doc on git use reccomendations for their project based on experiences in Accumulo and a similar Kafka document - http://accumulo.apache.org/git.html. It describes the options for committing feature branches as well. I propose using that as the current

Re: Preparation for Hive-1.2 release

Thanks Sushanth. Yes, blind applying the patch would work, but I believe it is a little more involved to keep the history (git merge, rebase, resolve, test, etc). I am doing the merge process again this time in git and regenerated what is hopefully an equivalent patch, hopefully I can get it done

Re: Preparation for Hive-1.2 release

Hi Szehon, Sergey tells me that he's verifying the repos, and expects to unblock it in another 20 minutes or so. I think that if HIVE-10347 is ready for commit now to svn, it should be committable to git as well, as-is as soon as that comes back up. In that scenario, there's no extra need to learn

Re: Preparation for Hive-1.2 release

Yes, I don't think it is fair to fork it this week, the change in question HIVE-10347 was reviewed and waiting 24 hours, but then svn repo is suddenly locked, and now the merge process has to be done again in git? I would vote to push it back one week to give everyone a chance to figure this out,

Re: Preparation for Hive-1.2 release

Since the svn repo is locked for git migration and a queue of patches are waiting to be committed, I'm not sure if forking on this Friday is realistic. HIVE-9726 is part of the merge (HIVE-10347) which is also in the queue. Thanks, Xuefu On Wed, Apr 22, 2015 at 9:55 AM, Sushanth Sowmyan wrote:

Re: Preparation for Hive-1.2 release

@Lefty : Yup, I've been following the other thread and https://issues.apache.org/jira/browse/INFRA-9488 - I think that'll stabilize before we fork. I'll definitely wait for it, but also wanted to do a reminder/call-for-patches before it. :) @Youngwoo: Thanks, I'll add that to the tracker. I do n

Re: Preparation for Hive-1.2 release

Hi, I would like to add a request for support Spark 1.3, HIVE-9726. Currently Apache Bigtop includes Spark 1.3 and we ran into a compatibility issue for Hive 1.1+. The issue have been resolved on 'spark-branch' but could not find a 'fix version' for it. I hope that the fix merge into release 1.2.

Re: Preparation for Hive-1.2 release

You might want to allow extra time for the transition to git, unless it goes very smoothly. Right now commits aren't possible. And for those that don't know, here's how to get wiki edit privileges: About This Wiki