You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Sergey Shelukhin <se...@hortonworks.com> on 2014/09/13 03:33:37 UTC
moving Hive to git
Hi.
Many Apache projects are moving to git from svn; HBase moved recently, and
as far as I have heard Hadoop has moved too.
Are there any objections to moving Hive to use git too?
I wanted to start a preliminary discussion.
--
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.
Re: moving Hive to git
Posted by Mohit Sabharwal <mo...@cloudera.com>.
Reg. disabling merge commits, if Apache is ok installing git server-side
hook scripts, setting up a pre-receive hook could be a possible option:
http://stackoverflow.com/questions/2039773/have-remote-git-repository-refuse-merge-commits-on-push
On Wed, Sep 17, 2014 at 10:56 AM, Sergey Shelukhin
<se...@hortonworks.com> wrote:
> I can check how HBase operates without merge commits... cherry-picking
> seems tedious, at least without the script - too easy to forget, and that
> would arguably be more harmful than a stray merge commit.
>
> On Wed, Sep 17, 2014 at 10:47 AM, Brock Noland <br...@cloudera.com> wrote:
>
>> Hi,
>>
>> I am generally +1 on the proposal. I'd strongly want to disable merge
>> commits. They are far too easy to accidently push. If there is no option to
>> disable them, one option would be to do what we did in flume.
>>
>> Basically:
>>
>> 1) Trunk operates as normal.
>> 2) We always have the next release branch open
>> 3) Every commit is committed to trunk and immediately cherry-picked to the
>> release branch. We could use a script to automate this.
>>
>> Brock
>>
>
> --
> 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.
Re: moving Hive to git
Posted by Sergey Shelukhin <se...@hortonworks.com>.
I can check how HBase operates without merge commits... cherry-picking
seems tedious, at least without the script - too easy to forget, and that
would arguably be more harmful than a stray merge commit.
On Wed, Sep 17, 2014 at 10:47 AM, Brock Noland <br...@cloudera.com> wrote:
> Hi,
>
> I am generally +1 on the proposal. I'd strongly want to disable merge
> commits. They are far too easy to accidently push. If there is no option to
> disable them, one option would be to do what we did in flume.
>
> Basically:
>
> 1) Trunk operates as normal.
> 2) We always have the next release branch open
> 3) Every commit is committed to trunk and immediately cherry-picked to the
> release branch. We could use a script to automate this.
>
> Brock
>
--
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.
Re: moving Hive to git
Posted by Brock Noland <br...@cloudera.com>.
Hi,
I am generally +1 on the proposal. I'd strongly want to disable merge
commits. They are far too easy to accidently push. If there is no option to
disable them, one option would be to do what we did in flume.
Basically:
1) Trunk operates as normal.
2) We always have the next release branch open
3) Every commit is committed to trunk and immediately cherry-picked to the
release branch. We could use a script to automate this.
Brock
Re: moving Hive to git
Posted by Owen O'Malley <om...@apache.org>.
For me, the advantages of git are:
1. Each user's working copy contains the global history of the project. So
while I'm disconnected in an airplane; I can look at history and logs,
switch between branches, and do merges.
2. It makes it very easy to work on development branches and rebase off of
trunk to incorporate other people's changes. Tracking of which commits have
been merged in to a branch is much better in git than subversion.
3. I can easily share my development branches with others via github (or
Apache if we switch).
4. Tags can be signed with pgp keys and unlike subversion, you can't commit
into tags by mistake.
Thanks,
Owen
On Wed, Sep 17, 2014 at 8:47 AM, Lefty Leverenz <le...@gmail.com>
wrote:
> I'm not convinced git would be better. Could someone please spell out the
> advantages?
>
> In particular:
>
>
> 1. "... git is more powerful and easy to use (once you go past the
> learning curve!)"
>
>
> -- Lefty
>
> On Tue, Sep 16, 2014 at 4:27 PM, Sergey Shelukhin <se...@hortonworks.com>
> wrote:
>
> > It seems there was consensus that we should move. Any volunteers to do
> it?
> > I can try to find the details on how HBase migrated.
> >
> > On Fri, Sep 12, 2014 at 7:10 PM, Lefty Leverenz <leftyleverenz@gmail.com
> >
> > wrote:
> >
> > > We had a related discussion March 5 - 10: llsmugcwkuryr5tb
> > > <http://markmail.org/message/llsmugcwkuryr5tb> through
> rq66qe2cpfgw7o5s
> > > <http://markmail.org/message/rq66qe2cpfgw7o5s>.
> > >
> > >
> > > -- Lefty
> > >
> > > On Fri, Sep 12, 2014 at 9:33 PM, Sergey Shelukhin <
> > sergey@hortonworks.com>
> > > wrote:
> > >
> > > > Hi.
> > > > Many Apache projects are moving to git from svn; HBase moved
> recently,
> > > and
> > > > as far as I have heard Hadoop has moved too.
> > > > Are there any objections to moving Hive to use git too?
> > > > I wanted to start a preliminary discussion.
> > > >
> > > > --
> > > > 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.
> >
>
Re: moving Hive to git
Posted by Lefty Leverenz <le...@gmail.com>.
I'm not convinced git would be better. Could someone please spell out the
advantages?
In particular:
1. "... git is more powerful and easy to use (once you go past the
learning curve!)"
-- Lefty
On Tue, Sep 16, 2014 at 4:27 PM, Sergey Shelukhin <se...@hortonworks.com>
wrote:
> It seems there was consensus that we should move. Any volunteers to do it?
> I can try to find the details on how HBase migrated.
>
> On Fri, Sep 12, 2014 at 7:10 PM, Lefty Leverenz <le...@gmail.com>
> wrote:
>
> > We had a related discussion March 5 - 10: llsmugcwkuryr5tb
> > <http://markmail.org/message/llsmugcwkuryr5tb> through rq66qe2cpfgw7o5s
> > <http://markmail.org/message/rq66qe2cpfgw7o5s>.
> >
> >
> > -- Lefty
> >
> > On Fri, Sep 12, 2014 at 9:33 PM, Sergey Shelukhin <
> sergey@hortonworks.com>
> > wrote:
> >
> > > Hi.
> > > Many Apache projects are moving to git from svn; HBase moved recently,
> > and
> > > as far as I have heard Hadoop has moved too.
> > > Are there any objections to moving Hive to use git too?
> > > I wanted to start a preliminary discussion.
> > >
> > > --
> > > 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.
>
Re: moving Hive to git
Posted by Sergey Shelukhin <se...@hortonworks.com>.
It seems there was consensus that we should move. Any volunteers to do it?
I can try to find the details on how HBase migrated.
On Fri, Sep 12, 2014 at 7:10 PM, Lefty Leverenz <le...@gmail.com>
wrote:
> We had a related discussion March 5 - 10: llsmugcwkuryr5tb
> <http://markmail.org/message/llsmugcwkuryr5tb> through rq66qe2cpfgw7o5s
> <http://markmail.org/message/rq66qe2cpfgw7o5s>.
>
>
> -- Lefty
>
> On Fri, Sep 12, 2014 at 9:33 PM, Sergey Shelukhin <se...@hortonworks.com>
> wrote:
>
> > Hi.
> > Many Apache projects are moving to git from svn; HBase moved recently,
> and
> > as far as I have heard Hadoop has moved too.
> > Are there any objections to moving Hive to use git too?
> > I wanted to start a preliminary discussion.
> >
> > --
> > 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.
Re: moving Hive to git
Posted by Lefty Leverenz <le...@gmail.com>.
We had a related discussion March 5 - 10: llsmugcwkuryr5tb
<http://markmail.org/message/llsmugcwkuryr5tb> through rq66qe2cpfgw7o5s
<http://markmail.org/message/rq66qe2cpfgw7o5s>.
-- Lefty
On Fri, Sep 12, 2014 at 9:33 PM, Sergey Shelukhin <se...@hortonworks.com>
wrote:
> Hi.
> Many Apache projects are moving to git from svn; HBase moved recently, and
> as far as I have heard Hadoop has moved too.
> Are there any objections to moving Hive to use git too?
> I wanted to start a preliminary discussion.
>
> --
> 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.
>