Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0AFB918523 for ; Thu, 18 Jun 2015 13:27:21 +0000 (UTC) Received: (qmail 90939 invoked by uid 500); 18 Jun 2015 13:27:20 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 90857 invoked by uid 500); 18 Jun 2015 13:27:20 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 90843 invoked by uid 99); 18 Jun 2015 13:27:20 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2015 13:27:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id AA7641A5CC8 for ; Thu, 18 Jun 2015 13:27:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.791 X-Spam-Level: * X-Spam-Status: No, score=1.791 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-1.108, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2zCSzmvzonXG for ; Thu, 18 Jun 2015 13:27:09 +0000 (UTC) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 5C9CC428E3 for ; Thu, 18 Jun 2015 13:27:08 +0000 (UTC) Received: by lbbti3 with SMTP id ti3so52258601lbb.1 for ; Thu, 18 Jun 2015 06:26:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IZVr4KPCvP6GBElbPaSkSLKbKD5q3qWpk6vODwJT2e4=; b=Nzj4s5X/3KuEWlWAf2W0ck6tbkKotY50ar3Bt+ysO1oFMvUnk40KmGZj45TFwxDZ+S F+fJmHOplAB8BruAkJF/7bWWm+RpKftQ/xpILOio/pN0D8IUOjyyLFUDMAynJr8BQ8qm HWAg8NbNer+9wJiiorqUTahXNtImMa78YtkktHbxBCzZ6fAqwMdH4qKdD6L/bRjTXewi 15pwQsNWmxFnsr1//sO81xgrNiHrrCwu8CY/EQ6k2JOvUgFaptHT6zprvwZ/ZRMk7Gsh H63D33OHnX/KmbFyQ/836Lw0w1/x5gdgc5ZpKzOXPYdHxSnFZYoT7I9zU5FjmWSSFkS3 yu4g== MIME-Version: 1.0 X-Received: by 10.152.29.234 with SMTP id n10mr12970242lah.101.1434633982314; Thu, 18 Jun 2015 06:26:22 -0700 (PDT) Received: by 10.112.34.197 with HTTP; Thu, 18 Jun 2015 06:26:22 -0700 (PDT) In-Reply-To: <558204AA.5080005@gmail.com> References: <556CA2B1.30406@hortonworks.com> <556CE19D.40505@gmail.com> <5581C2B6.2070801@gmail.com> <558204AA.5080005@gmail.com> Date: Thu, 18 Jun 2015 16:26:22 +0300 Message-ID: Subject: Re: PL/HQL and Hive From: Dmitry Tolpeko To: Alan Gates Cc: "dev@hive.apache.org" Content-Type: multipart/related; boundary=089e0158cba6e632fc0518cac025 --089e0158cba6e632fc0518cac025 Content-Type: multipart/alternative; boundary=089e0158cba6e632f90518cac024 --089e0158cba6e632f90518cac024 Content-Type: text/plain; charset=UTF-8 Thanks, Alan. I will update the package naming, and try to create Jira and patch soon. Dmitry On Thu, Jun 18, 2015 at 2:37 AM, Alan Gates wrote: > In Apache projects there are contributors and committers. Contributors > are anyone who helps with the project via code, docs, tests, bug reports, > etc. Committers can commit code, though it must still be reviewed by other > committers. On the process of becoming a committer in Hive see > https://cwiki.apache.org/confluence/display/Hive/BecomingACommitter > Obviously contributing a large bit of functionality starts you on that road > nicely. > > If you need help getting the patch together let me know. > > Alan. > > Dmitry Tolpeko > June 17, 2015 at 13:02 > Alan, > > HPL/SQL is a good name, I am ok with this change. Right now I am the only > one developer of PL/HQL. Which status will I be given in the Hive project, > so I can continue developing the tool? I will read docs and try to create a > patch. > > Thanks, > > Dmitry > > > Alan Gates > June 17, 2015 at 11:55 > Here's what we need to do: > > 1) You need to file a JIRA proposing to contribute the code. > 2) You can then contribute the code as a patch to that JIRA. As long as > you've written all the code yourself this is sufficient to hand legal > rights to Apache to contribute the code. If others beyond you have legal > claim to the code (ie they wrote it or paid you to write it) we'll need to > work with Apache and those authors to get clearance to include the code. > 3) Before committing the code we need to move it to an org.apache.hive > packaging structure. I propose that we put it in a new package > org.apache.hive.hplsql (see below for why I chose that). We can take the > patch you submit and make this change before committing or you can move it > yourself before you contribute the patch. > 4) One of the current committers can then take the patch and get it > committed. > > One suggestion that might be controversial: I propose we change the name > from PL/HQL to HPL/SQL (hence my packaging name suggestion above). We want > to move away from saying Hive has a language called HQL which is SQL like. > At this point Hive's SQL is most of the way to SQL-92 so talking about HQL > just confuses people. Hence Hive PL/SQL (HPL/SQL) seems better. Or if you > prefer we could do PL/HSQL. > > Alan. > > Dmitry Tolpeko > June 15, 2015 at 8:03 > Hi Alan, > > I am back from my vacation. Please let me know what actions, information > is required for me regarding IP. Can we talk about Jira creation and first > steps to make PL/HQL conform to Hive standards? > > Thanks, > > Dmitry > > > Dmitry Tolpeko > June 2, 2015 at 12:35 > Alan, > > I am new to the Hive project structure and development process, so I would > highly appreciate your guidance (if you can initiate Jira or tell me how to > do that i.e). Also I can grant software to Apache if required although I am > not sure which "IP clearance" required. For me uploading of the code is > sufficient. > > Thank you, > > Dmitry > > > Alan Gates > June 1, 2015 at 15:50 > Dmitry, > > I'm thrilled to hear that you're open to integrating PL/HQL into Hive. > > As for how we'd do it, this is obviously something we'll have to discuss > in the community on the dev list. But my initial thought is that we start > by importing it as it, mostly focussing on package name changes, etc. So > it starts as a stand alone. Then over time we work on integrating it > directly into Hive. This will have a number of benefits for users as > they'll be able to create and store procedures, invoke them from JDBC > connections, grant and revoke access to procedures, etc. > > So I think the next step is to open a JIRA on it and then we can start > building a patch to contribute the code. > > Given that PL/HQL has already been released as a separate entity I'm not > sure if we need additional IP clearance (ie you have to sign a grant) or if > you uploading the code to a JIRA is sufficient. Do any of the Hive PMC > know? > > No worries if you can't respond until June 12, there's no a rush. Enjoy > your vacation. > > Alan. > > > > --089e0158cba6e632f90518cac024 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, Alan. I will update the package naming, and try to= create Jira and patch soon.

Dmitry

On Thu, Jun 18, 2015 at 2:= 37 AM, Alan Gates <alanfgates@gmail.com> wrote:
In Apache projects there=20 are contributors and committers.=C2=A0 Contributors are anyone who helps wi= th the project via code, docs, tests, bug reports, etc.=C2=A0 Committers can= =20 commit code, though it must still be reviewed by other committers.=C2=A0 On= =20 the process of becoming a committer in Hive see=20 https://cwiki.apache.org/confluence/display/Hive/Bec= omingACommitter=C2=A0=20 Obviously contributing a large bit of functionality starts you on that=20 road nicely.

If you need help getting the patch together let me know.

Alan.

=20 June 17, 2015 at= =20 13:02
Alan,

HPL/SQL is a good name, I am ok with this change. Right now I am the only one=20 developer of PL/HQL. Which status will I be given in the Hive project,=20 so I can continue developing the tool? I will read docs and try to=20 create a patch.

Thanks,

D= mitry


=20 June 17, 2015 at= =20 11:55
Here's what we need to do:

1) You need to file a JIRA proposing to contribute the code.
2) You can then contribute the code as a patch to that JIRA.=C2=A0 As long = as you've written all the code yourself this is sufficient to hand legal= =20 rights to Apache to contribute the code.=C2=A0 If others beyond you have=20 legal claim to the code (ie they wrote it or paid you to write it) we'l= l need to work with Apache and those authors to get clearance to include=20 the code.
3) Before committing the code we need to move it to an org.apache.hive=20 packaging structure.=C2=A0 I propose that we put it in a new package=20 org.apache.hive.hplsql (see below for why I chose that).=C2=A0 We can take= =20 the patch you submit and make this change before committing or you can=20 move it yourself before you contribute the patch.
4) One of the current committers can then take the patch and get it=20 committed.

One suggestion that might be controversial:=C2=A0 I propose we change the= =20 name from PL/HQL to HPL/SQL (hence my packaging name suggestion above).=C2= =A0 We want to move away from saying Hive has a language called HQL which=20 is SQL like.=C2=A0 At this point Hive's SQL is most of the way to SQL-9= 2 so=20 talking about HQL just confuses people.=C2=A0 Hence Hive PL/SQL (HPL/SQL)= =20 seems better.=C2=A0 Or if you prefer we could do PL/HSQL.

Alan.

=20 June 15, 2015 at= =20 8:03
Hi Alan,

I am back from my vacation. Please let me know what actions, information=20 is required for me regarding IP. Can we talk about Jira creation and=20 first steps to make PL/HQL conform to Hive standards?

<= div>Thanks,

Dmitry


=20 June 2, 2015 at= =20 12:35
Alan,

I am new to the Hive project structure and development process, so I=20 would highly appreciate your guidance (if you can initiate Jira or tell=20 me how to do that i.e). Also I can grant software to Apache if required=20 although I am not sure which "IP clearance" required. For me uplo= ading=20 of the code is sufficient.

Thank you,=C2=A0
<= div>
Dmitry =C2=A0


=20 June 1, 2015 at= =20 15:50
Dmitry,

I'm thrilled to hear that you're open to integrating PL/HQL into Hi= ve.=C2=A0

As for how we'd do it, this is obviously something we'll have to di= scuss in the community on the dev list.=C2=A0 But my initial thought is that we= =20 start by importing it as it, mostly focussing on package name changes,=20 etc.=C2=A0 So it starts as a stand alone.=C2=A0 Then over time we work on= =20 integrating it directly into Hive.=C2=A0 This will have a number of benefit= s=20 for users as they'll be able to create and store procedures, invoke the= m from JDBC connections, grant and revoke access to procedures, etc.

So I think the next step is to open a JIRA on it and then we can start=20 building a patch to contribute the code.

Given that PL/HQL has already been released as a separate entity I'm no= t sure if we need additional IP clearance (ie you have to sign a grant)=20 or if you uploading the code to a JIRA is sufficient.=C2=A0 Do any of the= =20 Hive PMC know?

No worries if you can't respond until June 12, there's no a rush.= =C2=A0 Enjoy your vacation.

Alan.




--089e0158cba6e632f90518cac024-- --089e0158cba6e632fc0518cac025--