Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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 issues resolved.

There is still one final list that is not frozen, but the bar for this
is higher than the previous lists, and this list will remain open
until we wrap up this release. To request a JIRA for inclusion in this
list, it must qualify for one of the following three cases:

a) A product outage (i.e. causes a major feature of hive to not work,
without there being any workaround)
b) A regression (something, possibly a regular test used to work, but
no longer works as of this release)
c) A trivial change that carries no testing risk associated with it

All committers who have requested jiras for inclusion so far, please
try to get your patches in asap, and we'll get moving with the release
process. :)



On Thu, Apr 30, 2015 at 11:57 AM, Sushanth Sowmyan  wrote:
> 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 there for further inclusion requests,
> and for that, I've been phasing in strictness for the bar to include
> into that list.
>
> As of right now, the bar says "bugfixes only".
>
> As my original plan said, at 3:01PM PDT today, I had planned to raise
> that bar further, to become "critical bugfixes or trivial changes
> only". Since I did not send a reminder email yesterday night about
> this deadline, I extend this deadline to midnight tonight (defined as
> 00:01 AM PDT Friday May 1st 2015) for requests for inclusion for
> general purpose bugfixes.
>
> After this deadline passes, only bugfixes that are deemed to be
> product outages (i.e. no workarounds known, or a major feature of hive
> is disabled), or regressions discovered during testing of the RCs will
> be allowed to be included. Any jiras already present in that list will
> be included. After the deadline passes, I will create a release JIRA,
> and mark it blocked by all the jiras in the wiki.
>
> Examples of (fake) bugs that will be allowed in after this deadline:
>
> a) NPE whenever someone tries to use a union in a subquery clause =>
> Product outage - only workaround might be to not use unions or
> subqueries, which makes it impact a major feature of hive. Also,
> probably a regression.
> b) Changing an error message from "could not fnid appropriate config"
> to "could not find appropriate config" => trivial, and does not carry
> significant testing risk.
> c) TestSchemaTool discovered to fail for postgres. => Regression.
>
> Examples of (fake) bugs that would not be allowed for inclusion past
> this deadline:
> a) Implement OGRE (new fileformat, say) support in HCatalog =>
> Feature, not bug, and not critical bug
> b) Fix NPE when HCatalog attempts to read from OGRE (new fileformat,
> say) => Same as above, but phrased to sound like a bug - easy to test
> if we ask if it's a regression.
> c) Formatting of output from beeline to be customizable => Feature,
> not bug, and not critical bug, although smaller in scope than above.
> d) Fix default for orc.compress.dummy.setting to be 42 =>
> questionable. Might fly under the radar for being trivial enough if
> the setting does not carry enough testing risk, but at the same time,
> should have been requested for inclusion earlier.
>
> Issues that have already been asked for inclusion in the list at
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> will still be honoured, and considered release blockers unless the
> committer requesting inclusion and release manager agree that it can
> be removed.
>
> TL;DR : Deadline for general purpose bugfix inclusion into 1.2 is
> tonight, after that, I'm going to get more strict on whether or not I
> allow something in. If you already have a jira on that list, I will
> wait on its fix before moving forward, so you have a ticket on the 1.2
> train. That said, if you have a jira on that list, I will of course be
> breathing down your necks to make sure it gets in in time so that I
> can get the release process cracking. :p
>
> Thanks for reading!
> -Sushanth
>
> On Tue, Apr 28, 2015 at 1:33 AM, Sushanth Sowmyan  wrote:
>> 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, but no
>> new feature JIRAs will be included.
>>
>> The list is still open for any new bugfix jira to be added to the
>> list. I will start getting R

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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 there for further inclusion requests,
and for that, I've been phasing in strictness for the bar to include
into that list.

As of right now, the bar says "bugfixes only".

As my original plan said, at 3:01PM PDT today, I had planned to raise
that bar further, to become "critical bugfixes or trivial changes
only". Since I did not send a reminder email yesterday night about
this deadline, I extend this deadline to midnight tonight (defined as
00:01 AM PDT Friday May 1st 2015) for requests for inclusion for
general purpose bugfixes.

After this deadline passes, only bugfixes that are deemed to be
product outages (i.e. no workarounds known, or a major feature of hive
is disabled), or regressions discovered during testing of the RCs will
be allowed to be included. Any jiras already present in that list will
be included. After the deadline passes, I will create a release JIRA,
and mark it blocked by all the jiras in the wiki.

Examples of (fake) bugs that will be allowed in after this deadline:

a) NPE whenever someone tries to use a union in a subquery clause =>
Product outage - only workaround might be to not use unions or
subqueries, which makes it impact a major feature of hive. Also,
probably a regression.
b) Changing an error message from "could not fnid appropriate config"
to "could not find appropriate config" => trivial, and does not carry
significant testing risk.
c) TestSchemaTool discovered to fail for postgres. => Regression.

Examples of (fake) bugs that would not be allowed for inclusion past
this deadline:
a) Implement OGRE (new fileformat, say) support in HCatalog =>
Feature, not bug, and not critical bug
b) Fix NPE when HCatalog attempts to read from OGRE (new fileformat,
say) => Same as above, but phrased to sound like a bug - easy to test
if we ask if it's a regression.
c) Formatting of output from beeline to be customizable => Feature,
not bug, and not critical bug, although smaller in scope than above.
d) Fix default for orc.compress.dummy.setting to be 42 =>
questionable. Might fly under the radar for being trivial enough if
the setting does not carry enough testing risk, but at the same time,
should have been requested for inclusion earlier.

Issues that have already been asked for inclusion in the list at
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
will still be honoured, and considered release blockers unless the
committer requesting inclusion and release manager agree that it can
be removed.

TL;DR : Deadline for general purpose bugfix inclusion into 1.2 is
tonight, after that, I'm going to get more strict on whether or not I
allow something in. If you already have a jira on that list, I will
wait on its fix before moving forward, so you have a ticket on the 1.2
train. That said, if you have a jira on that list, I will of course be
breathing down your necks to make sure it gets in in time so that I
can get the release process cracking. :p

Thanks for reading!
-Sushanth

On Tue, Apr 28, 2015 at 1:33 AM, Sushanth Sowmyan  wrote:
> 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, but no
> new feature JIRAs will be included.
>
> The list is still open for any new bugfix jira to be added to the
> list. I will start getting RC0 ready now. The purpose of RC0 is not
> for it to be a true release-candidate, but simply to go through the
> process of creating a release, verifying instructions set to create a
> release, so that we can discover any hiccups along the way. Once that
> is done, the next deadline of note for the community is 15:01,
> Thursday, 30th Apr 2015 PDT, which is the deadline for requesting any
> bugfix jiras for inclusion.
>
> After this deadline, the list will go into further lockdown, and allow
> inclusion of only jiras already in the currently accepted lists, and
> either critical bugfixes which are product breakages without
> workarounds, or bugs discovered during testing of the RCs.
>
> Thanks,
> -Sushanth
>
>
>
> On Mon, Apr 27, 2015 at 4:51 PM, Sushanth Sowmyan  wrote:
>> 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 :  If you have any other jira you
>> want included for 1.2, please go and add it to
>> https://cwiki.apache.org/co

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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, but no
new feature JIRAs will be included.

The list is still open for any new bugfix jira to be added to the
list. I will start getting RC0 ready now. The purpose of RC0 is not
for it to be a true release-candidate, but simply to go through the
process of creating a release, verifying instructions set to create a
release, so that we can discover any hiccups along the way. Once that
is done, the next deadline of note for the community is 15:01,
Thursday, 30th Apr 2015 PDT, which is the deadline for requesting any
bugfix jiras for inclusion.

After this deadline, the list will go into further lockdown, and allow
inclusion of only jiras already in the currently accepted lists, and
either critical bugfixes which are product breakages without
workarounds, or bugs discovered during testing of the RCs.

Thanks,
-Sushanth



On Mon, Apr 27, 2015 at 4:51 PM, Sushanth Sowmyan  wrote:
> 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 :  If you have any other jira you
> want included for 1.2, please go and add it to
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>
> Tonight midnight will be the deadline for feature include requests,
> and this list will go on lockdown for any further requests for feature
> inclusions. Bugfixes will still be okay to request for inclusion.
>
>
>
> On Mon, Apr 27, 2015 at 4:41 PM, Sushanth Sowmyan  wrote:
>> 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, 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.
>>>
>>> Thanks,
>>> -Sushanth

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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 :  If you have any other jira you
want included for 1.2, please go and add it to
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status

Tonight midnight will be the deadline for feature include requests,
and this list will go on lockdown for any further requests for feature
inclusions. Bugfixes will still be okay to request for inclusion.



On Mon, Apr 27, 2015 at 4:41 PM, Sushanth Sowmyan  wrote:
> 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, 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.
>>
>> Thanks,
>> -Sushanth

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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, 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.
>
> Thanks,
> -Sushanth

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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.

Thanks,
-Sushanth

Re: Preparation for Hive-1.2 release

[Vinod Kumar Vavilapalli]

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.

Can Hive move to 2.7.0, at least with the initial intention of 
testing/validation?

Thanks,
+Vinod

[1] [ANNOUNCE] Apache Hadoop 2.7.0 Release 
http://markmail.org/thread/ytisa4w73ym4ee65

On Apr 21, 2015, at 8:33 PM, Sushanth Sowmyan 
mailto:khorg...@gmail.com>> wrote:

Hi Folks,

Per my mail 3 weeks back, we should start getting ready to release 1.2
as a rollup. And as per my proposal to manage this release, I'd like
to start off the process of forking 1.2, and making trunk 1.3.

I've set up a cwiki page for people to land development patches that
are almost done, to signal their desire that this be included in 1.2 :
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status

A rough timeline I see for this process would be to fork this Friday
(24th Apr), and then start rolling out RC0 by, say, Wednesday next
week. This would mean that I would request that if you want your jira
included in 1.2, it be close to completion, or have a patch available
for review. By mid next week, also, I expect to freeze the wiki
inclusion list for features, and keep it open only for bugfixes
discovered during testing the various RCs.

Please feel free to edit that jira with your requests, or, if you
don't have edit privileges, if you reply to this mail, I can add it
in. (Also, if you don't have wiki edit privileges, you should probably
ask for it. :p)

Thanks!
-Sushanth

Re: Preparation for Hive-1.2 release

[Szehon Ho]

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
make sure no regression.

Thanks
Szehon

On Sun, Apr 26, 2015 at 1:59 AM, Thejas Nair  wrote:

> 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 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 : Once this jira version is created, please use fix
> > version = 1.3.0 for any jiras you resolve in master.
> >
> > Also, please refer to
> > https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> > for a proposed timeline of how I expect release candidates and the
> > list for jira inclusion is intended to go for this release.
> >
> > Thanks!
> > -Sushanth
> >
> >
> > On Fri, Apr 24, 2015 at 5:21 PM, Sushanth Sowmyan 
> wrote:
> >> 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, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan 
> >>> wrote:
> >>>
>  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 couple of days of
>  issues with the svn->git merge, and getting precommit tests working
>  again (thanks Szehon/Sergio!), it looks like the big patches in that
>  list are now in trunk, and the remaining ones are easy enough to
>  dual-merge. If there are no further feature requests for inclusions,
>  then I intend to lock the jira for feature inclusions by Monday, and
>  then allow only bugfixes to be requested for inclusions.
> 
>  With the list of jiras as it stands currently, I think we should be
>  able to go ahead with creating a branch tonight (midnight PDT), file a
>  jira to update master to 1.3, and have that resolved by Monday.
> 
>  Szehon, once we have a separate branch, would it be okay to set up a
>  nightly test run on that branch?
> 
>  Then, on Monday, I'll start working on rolling out an RC0, so that we
>  can have an RC0 out by Wednesday.
> 
> 
> 
> 
>  On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair 
>  wrote:
>  > 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 hive git usage recommendation for now (until we feel a need
> to
>  > do things differently).
>  >
>  > I think we should update
>  > https://cwiki.apache.org/confluence/display/Hive/HowToContribute
> page
>  > to include this link. Any volunteers ?
>  >
>  > Thanks,
>  > Thejas
>  >
>  >
>  > On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho 
> wrote:
>  >> 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 soon.
>  >>
>  >> Thanks,
>  >> Szehon
>  >>
>  >> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan <
> khorg...@gmail.com>
>  >> wrote:
>  >>
>  >>> 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 how to do merges in git, since I would expect this to be
>  >>> ready before then. If the .patch file uploaded on HIVE-10347
> applies
>  

Re: Preparation for Hive-1.2 release

[Thejas Nair]

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 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 : Once this jira version is created, please use fix
> version = 1.3.0 for any jiras you resolve in master.
>
> Also, please refer to
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> for a proposed timeline of how I expect release candidates and the
> list for jira inclusion is intended to go for this release.
>
> Thanks!
> -Sushanth
>
>
> On Fri, Apr 24, 2015 at 5:21 PM, Sushanth Sowmyan  wrote:
>> 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, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan 
>>> wrote:
>>>
 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 couple of days of
 issues with the svn->git merge, and getting precommit tests working
 again (thanks Szehon/Sergio!), it looks like the big patches in that
 list are now in trunk, and the remaining ones are easy enough to
 dual-merge. If there are no further feature requests for inclusions,
 then I intend to lock the jira for feature inclusions by Monday, and
 then allow only bugfixes to be requested for inclusions.

 With the list of jiras as it stands currently, I think we should be
 able to go ahead with creating a branch tonight (midnight PDT), file a
 jira to update master to 1.3, and have that resolved by Monday.

 Szehon, once we have a separate branch, would it be okay to set up a
 nightly test run on that branch?

 Then, on Monday, I'll start working on rolling out an RC0, so that we
 can have an RC0 out by Wednesday.




 On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair 
 wrote:
 > 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 hive git usage recommendation for now (until we feel a need to
 > do things differently).
 >
 > I think we should update
 > https://cwiki.apache.org/confluence/display/Hive/HowToContribute page
 > to include this link. Any volunteers ?
 >
 > Thanks,
 > Thejas
 >
 >
 > On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho  wrote:
 >> 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 soon.
 >>
 >> Thanks,
 >> Szehon
 >>
 >> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
 >> wrote:
 >>
 >>> 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 how to do merges in git, since I would expect this to be
 >>> ready before then. If the .patch file uploaded on HIVE-10347 applies
 >>> appropriately on svn, then there should be no issues applying it to
 >>> git. I can help there too, if that helps.
 >>>
 >>> Also, I think forking is not that drastic a measure in git as it is in
 >>> svn, and merges are a bit easier to manage under git. I would still
 >>> like to go ahead with a friday/weekend fork, and allow people to
 >>> continue submitting patches for inclusion up until we roll out an RC0,
 >>> and then lock it for bugfixes. (Note : If there are any other jiras
 >>> you are working on that you want to see in this release, please go add
 >>> it to that wiki list :
 >>>
 https://cwiki.apache.

Re: Preparation for Hive-1.2 release

[Sergio Pena]

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 new changes are detected on a patch; and the current commit for 1.3.0
version contains new .sql files on the metastore upgrade scripts, but the
HMS test did not run because a patch does not exist for this.

Should we use a JIRA in future versions so that these HMS upgrade tests can
be executed, and the metastore can be verified for any bug added to the
.sql files?

- Sergio

On Sat, Apr 25, 2015 at 4: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 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 : Once this jira version is created, please use fix
> version = 1.3.0 for any jiras you resolve in master.
>
> Also, please refer to
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> for a proposed timeline of how I expect release candidates and the
> list for jira inclusion is intended to go for this release.
>
> Thanks!
> -Sushanth
>
>
> On Fri, Apr 24, 2015 at 5:21 PM, Sushanth Sowmyan 
> wrote:
> > 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, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan 
> >> wrote:
> >>
> >>> 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 couple of days of
> >>> issues with the svn->git merge, and getting precommit tests working
> >>> again (thanks Szehon/Sergio!), it looks like the big patches in that
> >>> list are now in trunk, and the remaining ones are easy enough to
> >>> dual-merge. If there are no further feature requests for inclusions,
> >>> then I intend to lock the jira for feature inclusions by Monday, and
> >>> then allow only bugfixes to be requested for inclusions.
> >>>
> >>> With the list of jiras as it stands currently, I think we should be
> >>> able to go ahead with creating a branch tonight (midnight PDT), file a
> >>> jira to update master to 1.3, and have that resolved by Monday.
> >>>
> >>> Szehon, once we have a separate branch, would it be okay to set up a
> >>> nightly test run on that branch?
> >>>
> >>> Then, on Monday, I'll start working on rolling out an RC0, so that we
> >>> can have an RC0 out by Wednesday.
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair 
> >>> wrote:
> >>> > 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 hive git usage recommendation for now (until we feel a need
> to
> >>> > do things differently).
> >>> >
> >>> > I think we should update
> >>> > https://cwiki.apache.org/confluence/display/Hive/HowToContribute
> page
> >>> > to include this link. Any volunteers ?
> >>> >
> >>> > Thanks,
> >>> > Thejas
> >>> >
> >>> >
> >>> > On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho 
> wrote:
> >>> >> 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 soon.
> >>> >>
> >>> >> Thanks,
> >>> >> Szehon
> >>> >>
> >>> >> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan <
> khorg...@gmail.com>
> >>> >> wrote:
> >>> >>
> >>> >>> 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 how to do merges in git, since I would expect this to be
> >>> >>> ready before then. If the .patch file uploaded on HIVE-10347
> 

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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 : Once this jira version is created, please use fix
version = 1.3.0 for any jiras you resolve in master.

Also, please refer to
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
for a proposed timeline of how I expect release candidates and the
list for jira inclusion is intended to go for this release.

Thanks!
-Sushanth


On Fri, Apr 24, 2015 at 5:21 PM, Sushanth Sowmyan  wrote:
> 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, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan 
>> wrote:
>>
>>> 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 couple of days of
>>> issues with the svn->git merge, and getting precommit tests working
>>> again (thanks Szehon/Sergio!), it looks like the big patches in that
>>> list are now in trunk, and the remaining ones are easy enough to
>>> dual-merge. If there are no further feature requests for inclusions,
>>> then I intend to lock the jira for feature inclusions by Monday, and
>>> then allow only bugfixes to be requested for inclusions.
>>>
>>> With the list of jiras as it stands currently, I think we should be
>>> able to go ahead with creating a branch tonight (midnight PDT), file a
>>> jira to update master to 1.3, and have that resolved by Monday.
>>>
>>> Szehon, once we have a separate branch, would it be okay to set up a
>>> nightly test run on that branch?
>>>
>>> Then, on Monday, I'll start working on rolling out an RC0, so that we
>>> can have an RC0 out by Wednesday.
>>>
>>>
>>>
>>>
>>> On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair 
>>> wrote:
>>> > 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 hive git usage recommendation for now (until we feel a need to
>>> > do things differently).
>>> >
>>> > I think we should update
>>> > https://cwiki.apache.org/confluence/display/Hive/HowToContribute page
>>> > to include this link. Any volunteers ?
>>> >
>>> > Thanks,
>>> > Thejas
>>> >
>>> >
>>> > On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho  wrote:
>>> >> 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 soon.
>>> >>
>>> >> Thanks,
>>> >> Szehon
>>> >>
>>> >> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
>>> >> wrote:
>>> >>
>>> >>> 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 how to do merges in git, since I would expect this to be
>>> >>> ready before then. If the .patch file uploaded on HIVE-10347 applies
>>> >>> appropriately on svn, then there should be no issues applying it to
>>> >>> git. I can help there too, if that helps.
>>> >>>
>>> >>> Also, I think forking is not that drastic a measure in git as it is in
>>> >>> svn, and merges are a bit easier to manage under git. I would still
>>> >>> like to go ahead with a friday/weekend fork, and allow people to
>>> >>> continue submitting patches for inclusion up until we roll out an RC0,
>>> >>> and then lock it for bugfixes. (Note : If there are any other jiras
>>> >>> you are working on that you want to see in this release, please go add
>>> >>> it to that wiki list :
>>> >>>
>>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>>> >>> )
>>> >>>
>>> >>> I would like to avoid a long-tail process as happened for 0.12.0 &
>>> >>> 0.13.0 if possible. This way, I think we'll have more time for
>>> >>> testing/solidifying.
>>> >>>
>>> >>> Thanks,
>>> >>> -Sushanth
>>> >>>
>>> >>> P.S: Also, for 

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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, Apr 24, 2015 at 1:25 PM, Sushanth Sowmyan 
> wrote:
>
>> 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 couple of days of
>> issues with the svn->git merge, and getting precommit tests working
>> again (thanks Szehon/Sergio!), it looks like the big patches in that
>> list are now in trunk, and the remaining ones are easy enough to
>> dual-merge. If there are no further feature requests for inclusions,
>> then I intend to lock the jira for feature inclusions by Monday, and
>> then allow only bugfixes to be requested for inclusions.
>>
>> With the list of jiras as it stands currently, I think we should be
>> able to go ahead with creating a branch tonight (midnight PDT), file a
>> jira to update master to 1.3, and have that resolved by Monday.
>>
>> Szehon, once we have a separate branch, would it be okay to set up a
>> nightly test run on that branch?
>>
>> Then, on Monday, I'll start working on rolling out an RC0, so that we
>> can have an RC0 out by Wednesday.
>>
>>
>>
>>
>> On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair 
>> wrote:
>> > 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 hive git usage recommendation for now (until we feel a need to
>> > do things differently).
>> >
>> > I think we should update
>> > https://cwiki.apache.org/confluence/display/Hive/HowToContribute page
>> > to include this link. Any volunteers ?
>> >
>> > Thanks,
>> > Thejas
>> >
>> >
>> > On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho  wrote:
>> >> 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 soon.
>> >>
>> >> Thanks,
>> >> Szehon
>> >>
>> >> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
>> >> wrote:
>> >>
>> >>> 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 how to do merges in git, since I would expect this to be
>> >>> ready before then. If the .patch file uploaded on HIVE-10347 applies
>> >>> appropriately on svn, then there should be no issues applying it to
>> >>> git. I can help there too, if that helps.
>> >>>
>> >>> Also, I think forking is not that drastic a measure in git as it is in
>> >>> svn, and merges are a bit easier to manage under git. I would still
>> >>> like to go ahead with a friday/weekend fork, and allow people to
>> >>> continue submitting patches for inclusion up until we roll out an RC0,
>> >>> and then lock it for bugfixes. (Note : If there are any other jiras
>> >>> you are working on that you want to see in this release, please go add
>> >>> it to that wiki list :
>> >>>
>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>> >>> )
>> >>>
>> >>> I would like to avoid a long-tail process as happened for 0.12.0 &
>> >>> 0.13.0 if possible. This way, I think we'll have more time for
>> >>> testing/solidifying.
>> >>>
>> >>> Thanks,
>> >>> -Sushanth
>> >>>
>> >>> P.S: Also, for additional reference, from the svn->git thread,
>> >>> http://accumulo.apache.org/git.html is a good quick reference.
>> >>>
>> >>> On Wed, Apr 22, 2015 at 11:31 AM, Szehon Ho 
>> wrote:
>> >>> > 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,
>> >>> > like how to do merges now.
>> >>> >
>> >>> > Thanks
>> >>> > Szehon
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang 
>> >>> wrote:
>> >>> >
>> >>> >> Since the svn repo is locked for git migration and a queue of
>> patche

Re: Preparation for Hive-1.2 release

[Szehon Ho]

>
> 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 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 couple of days of
> issues with the svn->git merge, and getting precommit tests working
> again (thanks Szehon/Sergio!), it looks like the big patches in that
> list are now in trunk, and the remaining ones are easy enough to
> dual-merge. If there are no further feature requests for inclusions,
> then I intend to lock the jira for feature inclusions by Monday, and
> then allow only bugfixes to be requested for inclusions.
>
> With the list of jiras as it stands currently, I think we should be
> able to go ahead with creating a branch tonight (midnight PDT), file a
> jira to update master to 1.3, and have that resolved by Monday.
>
> Szehon, once we have a separate branch, would it be okay to set up a
> nightly test run on that branch?
>
> Then, on Monday, I'll start working on rolling out an RC0, so that we
> can have an RC0 out by Wednesday.
>
>
>
>
> On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair 
> wrote:
> > 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 hive git usage recommendation for now (until we feel a need to
> > do things differently).
> >
> > I think we should update
> > https://cwiki.apache.org/confluence/display/Hive/HowToContribute page
> > to include this link. Any volunteers ?
> >
> > Thanks,
> > Thejas
> >
> >
> > On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho  wrote:
> >> 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 soon.
> >>
> >> Thanks,
> >> Szehon
> >>
> >> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
> >> wrote:
> >>
> >>> 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 how to do merges in git, since I would expect this to be
> >>> ready before then. If the .patch file uploaded on HIVE-10347 applies
> >>> appropriately on svn, then there should be no issues applying it to
> >>> git. I can help there too, if that helps.
> >>>
> >>> Also, I think forking is not that drastic a measure in git as it is in
> >>> svn, and merges are a bit easier to manage under git. I would still
> >>> like to go ahead with a friday/weekend fork, and allow people to
> >>> continue submitting patches for inclusion up until we roll out an RC0,
> >>> and then lock it for bugfixes. (Note : If there are any other jiras
> >>> you are working on that you want to see in this release, please go add
> >>> it to that wiki list :
> >>>
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> >>> )
> >>>
> >>> I would like to avoid a long-tail process as happened for 0.12.0 &
> >>> 0.13.0 if possible. This way, I think we'll have more time for
> >>> testing/solidifying.
> >>>
> >>> Thanks,
> >>> -Sushanth
> >>>
> >>> P.S: Also, for additional reference, from the svn->git thread,
> >>> http://accumulo.apache.org/git.html is a good quick reference.
> >>>
> >>> On Wed, Apr 22, 2015 at 11:31 AM, Szehon Ho 
> wrote:
> >>> > 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,
> >>> > like how to do merges now.
> >>> >
> >>> > Thanks
> >>> > Szehon
> >>> >
> >>> >
> >>> >
> >>> > On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang 
> >>> wrote:
> >>> >
> >>> >> 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,
> >

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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 couple of days of
issues with the svn->git merge, and getting precommit tests working
again (thanks Szehon/Sergio!), it looks like the big patches in that
list are now in trunk, and the remaining ones are easy enough to
dual-merge. If there are no further feature requests for inclusions,
then I intend to lock the jira for feature inclusions by Monday, and
then allow only bugfixes to be requested for inclusions.

With the list of jiras as it stands currently, I think we should be
able to go ahead with creating a branch tonight (midnight PDT), file a
jira to update master to 1.3, and have that resolved by Monday.

Szehon, once we have a separate branch, would it be okay to set up a
nightly test run on that branch?

Then, on Monday, I'll start working on rolling out an RC0, so that we
can have an RC0 out by Wednesday.




On Wed, Apr 22, 2015 at 4:01 PM, Thejas Nair  wrote:
> 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 hive git usage recommendation for now (until we feel a need to
> do things differently).
>
> I think we should update
> https://cwiki.apache.org/confluence/display/Hive/HowToContribute page
> to include this link. Any volunteers ?
>
> Thanks,
> Thejas
>
>
> On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho  wrote:
>> 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 soon.
>>
>> Thanks,
>> Szehon
>>
>> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
>> wrote:
>>
>>> 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 how to do merges in git, since I would expect this to be
>>> ready before then. If the .patch file uploaded on HIVE-10347 applies
>>> appropriately on svn, then there should be no issues applying it to
>>> git. I can help there too, if that helps.
>>>
>>> Also, I think forking is not that drastic a measure in git as it is in
>>> svn, and merges are a bit easier to manage under git. I would still
>>> like to go ahead with a friday/weekend fork, and allow people to
>>> continue submitting patches for inclusion up until we roll out an RC0,
>>> and then lock it for bugfixes. (Note : If there are any other jiras
>>> you are working on that you want to see in this release, please go add
>>> it to that wiki list :
>>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>>> )
>>>
>>> I would like to avoid a long-tail process as happened for 0.12.0 &
>>> 0.13.0 if possible. This way, I think we'll have more time for
>>> testing/solidifying.
>>>
>>> Thanks,
>>> -Sushanth
>>>
>>> P.S: Also, for additional reference, from the svn->git thread,
>>> http://accumulo.apache.org/git.html is a good quick reference.
>>>
>>> On Wed, Apr 22, 2015 at 11:31 AM, Szehon Ho  wrote:
>>> > 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,
>>> > like how to do merges now.
>>> >
>>> > Thanks
>>> > Szehon
>>> >
>>> >
>>> >
>>> > On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang 
>>> wrote:
>>> >
>>> >> 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:
>>> >>
>>> >> > @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 not

Re: Preparation for Hive-1.2 release

[Thejas Nair]

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 hive git usage recommendation for now (until we feel a need to
do things differently).

I think we should update
https://cwiki.apache.org/confluence/display/Hive/HowToContribute page
to include this link. Any volunteers ?

Thanks,
Thejas


On Wed, Apr 22, 2015 at 2:37 PM, Szehon Ho  wrote:
> 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 soon.
>
> Thanks,
> Szehon
>
> On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
> wrote:
>
>> 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 how to do merges in git, since I would expect this to be
>> ready before then. If the .patch file uploaded on HIVE-10347 applies
>> appropriately on svn, then there should be no issues applying it to
>> git. I can help there too, if that helps.
>>
>> Also, I think forking is not that drastic a measure in git as it is in
>> svn, and merges are a bit easier to manage under git. I would still
>> like to go ahead with a friday/weekend fork, and allow people to
>> continue submitting patches for inclusion up until we roll out an RC0,
>> and then lock it for bugfixes. (Note : If there are any other jiras
>> you are working on that you want to see in this release, please go add
>> it to that wiki list :
>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>> )
>>
>> I would like to avoid a long-tail process as happened for 0.12.0 &
>> 0.13.0 if possible. This way, I think we'll have more time for
>> testing/solidifying.
>>
>> Thanks,
>> -Sushanth
>>
>> P.S: Also, for additional reference, from the svn->git thread,
>> http://accumulo.apache.org/git.html is a good quick reference.
>>
>> On Wed, Apr 22, 2015 at 11:31 AM, Szehon Ho  wrote:
>> > 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,
>> > like how to do merges now.
>> >
>> > Thanks
>> > Szehon
>> >
>> >
>> >
>> > On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang 
>> wrote:
>> >
>> >> 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:
>> >>
>> >> > @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 not see a commit on it in
>> >> > trunk for it, so I'll ping Brock on that bug to see if it's included
>> >> > through some other jira on trunk.
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Apr 21, 2015 at 10:58 PM, 김영우  wrote:
>> >> > > 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.
>> >> > >
>> >> > > Thanks,
>> >> > > Youngwoo
>> >> > >
>> >> > > On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan <
>> khorg...@gmail.com
>> >> >
>> >> > > wrote:
>> >> > >
>> >> > >> Hi Folks,
>> >> > >>
>> >> > >> Per my mail 3 weeks back, we should start getting ready to release
>> 1.2
>> >> > >> as a rollup. And as per my proposal to manage this release, I'd
>> like
>> >> > >> to start off the process of forking 1.2, and making trunk 1.3.
>> >> > >>
>> >> > >> I've set up a cwiki page for people to land development patches
>> that
>> >> > >> are almost done, to signal their desire that this be included in
>> 1.2 :
>> >> > >>
>> >> >
>> https://cwiki.apache.org/conflu

Re: Preparation for Hive-1.2 release

[Szehon Ho]

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 soon.

Thanks,
Szehon

On Wed, Apr 22, 2015 at 1:33 PM, Sushanth Sowmyan 
wrote:

> 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 how to do merges in git, since I would expect this to be
> ready before then. If the .patch file uploaded on HIVE-10347 applies
> appropriately on svn, then there should be no issues applying it to
> git. I can help there too, if that helps.
>
> Also, I think forking is not that drastic a measure in git as it is in
> svn, and merges are a bit easier to manage under git. I would still
> like to go ahead with a friday/weekend fork, and allow people to
> continue submitting patches for inclusion up until we roll out an RC0,
> and then lock it for bugfixes. (Note : If there are any other jiras
> you are working on that you want to see in this release, please go add
> it to that wiki list :
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> )
>
> I would like to avoid a long-tail process as happened for 0.12.0 &
> 0.13.0 if possible. This way, I think we'll have more time for
> testing/solidifying.
>
> Thanks,
> -Sushanth
>
> P.S: Also, for additional reference, from the svn->git thread,
> http://accumulo.apache.org/git.html is a good quick reference.
>
> On Wed, Apr 22, 2015 at 11:31 AM, Szehon Ho  wrote:
> > 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,
> > like how to do merges now.
> >
> > Thanks
> > Szehon
> >
> >
> >
> > On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang 
> wrote:
> >
> >> 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:
> >>
> >> > @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 not see a commit on it in
> >> > trunk for it, so I'll ping Brock on that bug to see if it's included
> >> > through some other jira on trunk.
> >> >
> >> >
> >> >
> >> > On Tue, Apr 21, 2015 at 10:58 PM, 김영우  wrote:
> >> > > 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.
> >> > >
> >> > > Thanks,
> >> > > Youngwoo
> >> > >
> >> > > On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan <
> khorg...@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > >> Hi Folks,
> >> > >>
> >> > >> Per my mail 3 weeks back, we should start getting ready to release
> 1.2
> >> > >> as a rollup. And as per my proposal to manage this release, I'd
> like
> >> > >> to start off the process of forking 1.2, and making trunk 1.3.
> >> > >>
> >> > >> I've set up a cwiki page for people to land development patches
> that
> >> > >> are almost done, to signal their desire that this be included in
> 1.2 :
> >> > >>
> >> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> >> > >>
> >> > >> A rough timeline I see for this process would be to fork this
> Friday
> >> > >> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
> >> > >> week. This would mean that I would request that if you want your
> jira
> >> > >> included in 1.2, it be close to completion, or have a patch
> available
> >> > >> for review. By mid next week, also, I expect to freeze the wiki
> >> > >> inclusion list for features, and keep it open only for bugfixes
> >> > >> discovered during testing the various RCs.
> >> > >>
> >> > >> Please feel free to edit that jira with your requests, or, if you
> >> > >> don't have edit privileges, if you reply to this mail,

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

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 how to do merges in git, since I would expect this to be
ready before then. If the .patch file uploaded on HIVE-10347 applies
appropriately on svn, then there should be no issues applying it to
git. I can help there too, if that helps.

Also, I think forking is not that drastic a measure in git as it is in
svn, and merges are a bit easier to manage under git. I would still
like to go ahead with a friday/weekend fork, and allow people to
continue submitting patches for inclusion up until we roll out an RC0,
and then lock it for bugfixes. (Note : If there are any other jiras
you are working on that you want to see in this release, please go add
it to that wiki list :
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
)

I would like to avoid a long-tail process as happened for 0.12.0 &
0.13.0 if possible. This way, I think we'll have more time for
testing/solidifying.

Thanks,
-Sushanth

P.S: Also, for additional reference, from the svn->git thread,
http://accumulo.apache.org/git.html is a good quick reference.

On Wed, Apr 22, 2015 at 11:31 AM, Szehon Ho  wrote:
> 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,
> like how to do merges now.
>
> Thanks
> Szehon
>
>
>
> On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang  wrote:
>
>> 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:
>>
>> > @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 not see a commit on it in
>> > trunk for it, so I'll ping Brock on that bug to see if it's included
>> > through some other jira on trunk.
>> >
>> >
>> >
>> > On Tue, Apr 21, 2015 at 10:58 PM, 김영우  wrote:
>> > > 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.
>> > >
>> > > Thanks,
>> > > Youngwoo
>> > >
>> > > On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan > >
>> > > wrote:
>> > >
>> > >> Hi Folks,
>> > >>
>> > >> Per my mail 3 weeks back, we should start getting ready to release 1.2
>> > >> as a rollup. And as per my proposal to manage this release, I'd like
>> > >> to start off the process of forking 1.2, and making trunk 1.3.
>> > >>
>> > >> I've set up a cwiki page for people to land development patches that
>> > >> are almost done, to signal their desire that this be included in 1.2 :
>> > >>
>> > https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>> > >>
>> > >> A rough timeline I see for this process would be to fork this Friday
>> > >> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
>> > >> week. This would mean that I would request that if you want your jira
>> > >> included in 1.2, it be close to completion, or have a patch available
>> > >> for review. By mid next week, also, I expect to freeze the wiki
>> > >> inclusion list for features, and keep it open only for bugfixes
>> > >> discovered during testing the various RCs.
>> > >>
>> > >> Please feel free to edit that jira with your requests, or, if you
>> > >> don't have edit privileges, if you reply to this mail, I can add it
>> > >> in. (Also, if you don't have wiki edit privileges, you should probably
>> > >> ask for it. :p)
>> > >>
>> > >> Thanks!
>> > >> -Sushanth
>> > >>
>> >
>>

Re: Preparation for Hive-1.2 release

[Szehon Ho]

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,
like how to do merges now.

Thanks
Szehon



On Wed, Apr 22, 2015 at 11:10 AM, Xuefu Zhang  wrote:

> 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:
>
> > @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 not see a commit on it in
> > trunk for it, so I'll ping Brock on that bug to see if it's included
> > through some other jira on trunk.
> >
> >
> >
> > On Tue, Apr 21, 2015 at 10:58 PM, 김영우  wrote:
> > > 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.
> > >
> > > Thanks,
> > > Youngwoo
> > >
> > > On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan  >
> > > wrote:
> > >
> > >> Hi Folks,
> > >>
> > >> Per my mail 3 weeks back, we should start getting ready to release 1.2
> > >> as a rollup. And as per my proposal to manage this release, I'd like
> > >> to start off the process of forking 1.2, and making trunk 1.3.
> > >>
> > >> I've set up a cwiki page for people to land development patches that
> > >> are almost done, to signal their desire that this be included in 1.2 :
> > >>
> > https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> > >>
> > >> A rough timeline I see for this process would be to fork this Friday
> > >> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
> > >> week. This would mean that I would request that if you want your jira
> > >> included in 1.2, it be close to completion, or have a patch available
> > >> for review. By mid next week, also, I expect to freeze the wiki
> > >> inclusion list for features, and keep it open only for bugfixes
> > >> discovered during testing the various RCs.
> > >>
> > >> Please feel free to edit that jira with your requests, or, if you
> > >> don't have edit privileges, if you reply to this mail, I can add it
> > >> in. (Also, if you don't have wiki edit privileges, you should probably
> > >> ask for it. :p)
> > >>
> > >> Thanks!
> > >> -Sushanth
> > >>
> >
>

Re: Preparation for Hive-1.2 release

[Xuefu Zhang]

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:

> @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 not see a commit on it in
> trunk for it, so I'll ping Brock on that bug to see if it's included
> through some other jira on trunk.
>
>
>
> On Tue, Apr 21, 2015 at 10:58 PM, 김영우  wrote:
> > 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.
> >
> > Thanks,
> > Youngwoo
> >
> > On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan 
> > wrote:
> >
> >> Hi Folks,
> >>
> >> Per my mail 3 weeks back, we should start getting ready to release 1.2
> >> as a rollup. And as per my proposal to manage this release, I'd like
> >> to start off the process of forking 1.2, and making trunk 1.3.
> >>
> >> I've set up a cwiki page for people to land development patches that
> >> are almost done, to signal their desire that this be included in 1.2 :
> >>
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
> >>
> >> A rough timeline I see for this process would be to fork this Friday
> >> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
> >> week. This would mean that I would request that if you want your jira
> >> included in 1.2, it be close to completion, or have a patch available
> >> for review. By mid next week, also, I expect to freeze the wiki
> >> inclusion list for features, and keep it open only for bugfixes
> >> discovered during testing the various RCs.
> >>
> >> Please feel free to edit that jira with your requests, or, if you
> >> don't have edit privileges, if you reply to this mail, I can add it
> >> in. (Also, if you don't have wiki edit privileges, you should probably
> >> ask for it. :p)
> >>
> >> Thanks!
> >> -Sushanth
> >>
>

Re: Preparation for Hive-1.2 release

[Sushanth Sowmyan]

@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 not see a commit on it in
trunk for it, so I'll ping Brock on that bug to see if it's included
through some other jira on trunk.



On Tue, Apr 21, 2015 at 10:58 PM, 김영우  wrote:
> 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.
>
> Thanks,
> Youngwoo
>
> On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan 
> wrote:
>
>> Hi Folks,
>>
>> Per my mail 3 weeks back, we should start getting ready to release 1.2
>> as a rollup. And as per my proposal to manage this release, I'd like
>> to start off the process of forking 1.2, and making trunk 1.3.
>>
>> I've set up a cwiki page for people to land development patches that
>> are almost done, to signal their desire that this be included in 1.2 :
>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>>
>> A rough timeline I see for this process would be to fork this Friday
>> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
>> week. This would mean that I would request that if you want your jira
>> included in 1.2, it be close to completion, or have a patch available
>> for review. By mid next week, also, I expect to freeze the wiki
>> inclusion list for features, and keep it open only for bugfixes
>> discovered during testing the various RCs.
>>
>> Please feel free to edit that jira with your requests, or, if you
>> don't have edit privileges, if you reply to this mail, I can add it
>> in. (Also, if you don't have wiki edit privileges, you should probably
>> ask for it. :p)
>>
>> Thanks!
>> -Sushanth
>>

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.

Thanks,
Youngwoo

On Wed, Apr 22, 2015 at 12:33 PM, Sushanth Sowmyan 
wrote:

> Hi Folks,
>
> Per my mail 3 weeks back, we should start getting ready to release 1.2
> as a rollup. And as per my proposal to manage this release, I'd like
> to start off the process of forking 1.2, and making trunk 1.3.
>
> I've set up a cwiki page for people to land development patches that
> are almost done, to signal their desire that this be included in 1.2 :
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>
> A rough timeline I see for this process would be to fork this Friday
> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
> week. This would mean that I would request that if you want your jira
> included in 1.2, it be close to completion, or have a patch available
> for review. By mid next week, also, I expect to freeze the wiki
> inclusion list for features, and keep it open only for bugfixes
> discovered during testing the various RCs.
>
> Please feel free to edit that jira with your requests, or, if you
> don't have edit privileges, if you reply to this mail, I can add it
> in. (Also, if you don't have wiki edit privileges, you should probably
> ask for it. :p)
>
> Thanks!
> -Sushanth
>

Re: Preparation for Hive-1.2 release

[Lefty Leverenz]

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

.

-- Lefty

On Tue, Apr 21, 2015 at 11:33 PM, Sushanth Sowmyan 
wrote:

> Hi Folks,
>
> Per my mail 3 weeks back, we should start getting ready to release 1.2
> as a rollup. And as per my proposal to manage this release, I'd like
> to start off the process of forking 1.2, and making trunk 1.3.
>
> I've set up a cwiki page for people to land development patches that
> are almost done, to signal their desire that this be included in 1.2 :
> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status
>
> A rough timeline I see for this process would be to fork this Friday
> (24th Apr), and then start rolling out RC0 by, say, Wednesday next
> week. This would mean that I would request that if you want your jira
> included in 1.2, it be close to completion, or have a patch available
> for review. By mid next week, also, I expect to freeze the wiki
> inclusion list for features, and keep it open only for bugfixes
> discovered during testing the various RCs.
>
> Please feel free to edit that jira with your requests, or, if you
> don't have edit privileges, if you reply to this mail, I can add it
> in. (Also, if you don't have wiki edit privileges, you should probably
> ask for it. :p)
>
> Thanks!
> -Sushanth
>

Preparation for Hive-1.2 release

[Sushanth Sowmyan]

Hi Folks,

Per my mail 3 weeks back, we should start getting ready to release 1.2
as a rollup. And as per my proposal to manage this release, I'd like
to start off the process of forking 1.2, and making trunk 1.3.

I've set up a cwiki page for people to land development patches that
are almost done, to signal their desire that this be included in 1.2 :
https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status

A rough timeline I see for this process would be to fork this Friday
(24th Apr), and then start rolling out RC0 by, say, Wednesday next
week. This would mean that I would request that if you want your jira
included in 1.2, it be close to completion, or have a patch available
for review. By mid next week, also, I expect to freeze the wiki
inclusion list for features, and keep it open only for bugfixes
discovered during testing the various RCs.

Please feel free to edit that jira with your requests, or, if you
don't have edit privileges, if you reply to this mail, I can add it
in. (Also, if you don't have wiki edit privileges, you should probably
ask for it. :p)

Thanks!
-Sushanth