hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thejas Nair <the...@hortonworks.com>
Subject Re: Created branch 1.0
Date Thu, 22 Jan 2015 00:35:12 GMT
As discussed in the previous thread [1] I don't see why it would be
horribly confusing to have-  1.0.0 = 0.14 + changes to delete things
due to deprecation + additional API documentation. 0.15 would then
become 1.1.0 .
I should be able to submit some patches for documenting public APIs by
tomorrow. I think we should be able to make the additional changes as
listed above in 2-3 days.

0.14 has already been stabilized, as a result getting an RC out of
that is going to be fast. Vikram has already started the preparations
such as generating the javadoc. For 0.15, the targeted date for first
RC is only Feb 9. So 1.0 would easily be out before 1.1 (based on
0.15).  Also, if you look at history of hive releases, it has taken
more than a month to find and resolve all the critical fixes after
branching.

It would be good to base the first 1.0 release on a branch of hive
that has been out for sometime, to ensure a very stable first 1.0
release. HIVE-6977 to delete HiveServer1 is already part of the thread
(looks like it got missed in most recent email from Vikram).

[1] Easier to follow the old thread on search-hadoop.com -
http://search-hadoop.com/m/8er9IQqJz/Apache+Hive+1.0&subj=Apache+Hive+1+0+



On Wed, Jan 21, 2015 at 3:39 PM, Brock Noland <brock@cloudera.com> wrote:
> Hi,
>
> I should have just waited to check where this branch came from, but I
> was quite surprised when I received this mail so I too quickly fired
> off a response. I apologize to everyone for the spam. The reason I was
> surprised is that I don't feel there was a consenus comming out of the
> 1.0 discussion: http://s.apache.org/hive-1.0-discuss
>
> As mentioned in that thread, I am not favor of creating 1.0 from 0.14.
> That will be horribly confusing. Too avoid confusion amongst our
> users, and indeed our developers, the 1.0 branch should be created
> from trunk and be a superset of the 0.15 release (minus anything we
> delete due to depreciation).
>
> Additionally, as Bill expressed on that thread, I see defining our
> public API as a big aspect of moving to a 1.0.
>
> Cheers.
> Brock
>
> On Wed, Jan 21, 2015 at 3:28 PM, Lefty Leverenz <leftyleverenz@gmail.com> wrote:
>> So my initial impression was correct -- instead of calling it release
>> 0.14.1, we're calling it 1.0.0.  Or am I hopelessly confused?
>>
>> Will 0.15.0 be 1.1.0?  (If so, I'll need to edit a dozen wikidocs.)
>>
>> Will release numbers get changed in JIRA issues?  Presumably that's not
>> possible in old comments, so we should document the equivalences
>> somewhere.  A JIRA issue for that with a well-phrased summary could help
>> future searchers.
>>
>>
>> -- Lefty
>>
>> On Wed, Jan 21, 2015 at 2:47 PM, Eugene Koifman <ekoifman@hortonworks.com>
>> wrote:
>>
>>> could we include HIVE-9390 & HIVE-9404?  This has been committed to trunk.
>>> They add useful retry logic to support insert/update/delete functionality.
>>>
>>> On Wed, Jan 21, 2015 at 1:06 PM, Vikram Dixit K <vikram.dixit@gmail.com>
>>> wrote:
>>>
>>> > Hi Folks,
>>> >
>>> > I have created branch 1.0 as discussed earlier. All the jiras that have
>>> > 0.14 as the fix version should be committed to 1.0 branch instead. The
>>> list
>>> > of jiras that are being tracked for 1.0 are as follows:
>>> >
>>> > HIVE-8485
>>> > HIVE-9053
>>> > HIVE-8996.
>>> >
>>> > Please let me know if you want to include more jiras here. I am working
>>> on
>>> > generating javadocs for this. I hope to have an RC out once these jiras
>>> get
>>> > in.
>>> >
>>> > Regards
>>> > Vikram.
>>> >
>>> > On Tue, Jan 20, 2015 at 1:00 PM, Vaibhav Gumashta <
>>> > vgumashta@hortonworks.com
>>> > > wrote:
>>> >
>>> > > Hi Vikram,
>>> > >
>>> > > I'd like to get this in: HIVE-8890
>>> > > <https://issues.apache.org/jira/browse/HIVE-8890> [HiveServer2
dynamic
>>> > > service discovery: use persistent ephemeral nodes curator recipe].
>>> > >
>>> > > Thanks,
>>> > > --Vaibhav
>>> > >
>>> > > On Mon, Jan 19, 2015 at 9:29 PM, Alan Gates <gates@hortonworks.com>
>>> > wrote:
>>> > >
>>> > > > I'd really like to get HIVE-8966 in there, since it breaks streaming
>>> > > > ingest.  The patch is ready to go, it's just waiting on a review,
>>> which
>>> > > > Owen has promised to do soon.
>>> > > >
>>> > > > Alan.
>>> > > >
>>> > > >   Vikram Dixit K <vikram.dixit@gmail.com>
>>> > > >  January 19, 2015 at 18:53
>>> > > > Hi All,
>>> > > >
>>> > > > I am going to be creating the branch 1.0 as mentioned earlier,
>>> > tomorrow.
>>> > > I
>>> > > > have the following list of jiras that I want to get committed
to the
>>> > > branch
>>> > > > before creating an RC.
>>> > > >
>>> > > > HIVE-9112
>>> > > > HIVE-6997 : Delete hive server 1
>>> > > > HIVE-8485
>>> > > > HIVE-9053
>>> > > >
>>> > > > Please let me know if you would like me to include any other jiras.
>>> > > >
>>> > > > Thanks
>>> > > > Vikram.
>>> > > >
>>> > > >
>>> > > > On Fri, Jan 16, 2015 at 1:35 PM, Vikram Dixit K <
>>> > vikram.dixit@gmail.com>
>>> > > > <vikram.dixit@gmail.com>
>>> > > >
>>> > > >
>>> > > >
>>> > > >   Thejas Nair <thejas@hortonworks.com>
>>> > > >  January 1, 2015 at 10:23
>>> > > > Yes, 1.0 is a good opportunity to remove some of the deprecated
>>> > > > components. The change to remove HiveServer1 is already there
in
>>> trunk
>>> > > > , we should include that.
>>> > > > We can also use 1.0 release to clarify the public vs private status
>>> of
>>> > > > some of the APIs.
>>> > > >
>>> > > > Thanks for the reminder about the documentation status of 1.0.
I will
>>> > > > look at some of them.
>>> > > >
>>> > > >
>>> > > > On Wed, Dec 31, 2014 at 12:12 AM, Lefty Leverenz
>>> > > >
>>> > > >   Lefty Leverenz <leftyleverenz@gmail.com>
>>> > > >  December 31, 2014 at 0:12
>>> > > > Oh, now I get it. The 1.0.0 *branch* of Hive. Okay.
>>> > > >
>>> > > > -- Lefty
>>> > > >
>>> > > > On Tue, Dec 30, 2014 at 11:43 PM, Lefty Leverenz <
>>> > > leftyleverenz@gmail.com>
>>> > > > <leftyleverenz@gmail.com>
>>> > > >
>>> > > >   Lefty Leverenz <leftyleverenz@gmail.com>
>>> > > >  December 30, 2014 at 23:43
>>> > > > I thought x.x.# releases were just for fixups, x.#.x could include
>>> new
>>> > > > features, and #.x.x were major releases that might have some
>>> > > > backward-incompatible changes. But I guess we haven't agreed on
that.
>>> > > >
>>> > > > As for documentation, we still have 84 jiras with TODOC14 labels
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC14
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC14
>>> > > >
>>> > > > .
>>> > > > Not to mention 25 TODOC13 labels
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC13
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC13
>>> > > >
>>> > > > ,
>>> > > > eleven TODOC12
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC12
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC12
>>> > > >
>>> > > > ,
>>> > > > seven TODOC11
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC11
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC11
>>> > > >
>>> > > > ,
>>> > > > and seven TODOC10
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC10
>>> > > >
>>> > > > <
>>> > >
>>> >
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20AND%20labels%20%3D%20TODOC10
>>> > > >
>>> > > > .
>>> > > >
>>> > > > That's 134 doc tasks to finish for a Hive 1.0.0 release -- preferably
>>> > by
>>> > > > the release date, not after. Because expectations are higher for
>>> 1.0.0
>>> > > > releases.
>>> > > >
>>> > > >
>>> > > > -- Lefty
>>> > > >
>>> > > > On Tue, Dec 30, 2014 at 5:23 PM, Vikram Dixit K <
>>> > vikram.dixit@gmail.com>
>>> > > > <vikram.dixit@gmail.com>
>>> > > >
>>> > > >   Vikram Dixit K <vikram.dixit@gmail.com>
>>> > > >  December 30, 2014 at 17:23
>>> > > > Hi Folks,
>>> > > >
>>> > > > Given that there have been a number of fixes that have gone into
>>> branch
>>> > > > 0.14 in the past 8 weeks, I would like to make a release of 0.14.1
>>> > soon.
>>> > > I
>>> > > > would like to fix some of the release issues as well this time
>>> around.
>>> > I
>>> > > am
>>> > > > thinking of some time around 15th January for getting a RC out.
>>> Please
>>> > > let
>>> > > > me know if you have any concerns. Also, from a previous thread,
I
>>> would
>>> > > > like to make this release the 1.0 branch of hive. The process
for
>>> > getting
>>> > > > jiras into this release is going to be the same as the previous
one
>>> > viz.:
>>> > > >
>>> > > > 1. Mark the jira with fix version 0.14.1 and update the status
to
>>> > > > blocker/critical.
>>> > > > 2. If a committer +1s the patch for 0.14.1, it is good to go in.
>>> Please
>>> > > > mention me in the jira in case you are not sure if the jira should
>>> make
>>> > > it
>>> > > > for 0.14.1.
>>> > > >
>>> > > > Thanks
>>> > > > Vikram.
>>> > > >
>>> > > >
>>> > > > CONFIDENTIALITY NOTICE
>>> > > > NOTICE: This message is intended for the use of the individual
or
>>> > entity
>>> > > > to which it is addressed and may contain information that is
>>> > > confidential,
>>> > > > privileged and exempt from disclosure under applicable law. If
the
>>> > reader
>>> > > > of this message is not the intended recipient, you are hereby
>>> notified
>>> > > that
>>> > > > any printing, copying, dissemination, distribution, disclosure
or
>>> > > > forwarding of this communication is strictly prohibited. If you
have
>>> > > > received this communication in error, please contact the sender
>>> > > immediately
>>> > > > and delete it from your system. Thank You.
>>> > > >
>>> > >
>>> > > --
>>> > > CONFIDENTIALITY NOTICE
>>> > > NOTICE: This message is intended for the use of the individual or
>>> entity
>>> > to
>>> > > which it is addressed and may contain information that is confidential,
>>> > > privileged and exempt from disclosure under applicable law. If the
>>> reader
>>> > > of this message is not the intended recipient, you are hereby notified
>>> > that
>>> > > any printing, copying, dissemination, distribution, disclosure or
>>> > > forwarding of this communication is strictly prohibited. If you have
>>> > > received this communication in error, please contact the sender
>>> > immediately
>>> > > and delete it from your system. Thank You.
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Nothing better than when appreciated for hard work.
>>> > -Mark
>>> >
>>>
>>>
>>>
>>> --
>>>
>>> Thanks,
>>> Eugene
>>>
>>> --
>>> CONFIDENTIALITY NOTICE
>>> NOTICE: This message is intended for the use of the individual or entity to
>>> which it is addressed and may contain information that is confidential,
>>> privileged and exempt from disclosure under applicable law. If the reader
>>> of this message is not the intended recipient, you are hereby notified that
>>> any printing, copying, dissemination, distribution, disclosure or
>>> forwarding of this communication is strictly prohibited. If you have
>>> received this communication in error, please contact the sender immediately
>>> and delete it from your system. Thank You.
>>>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
View raw message