Re: PL/HQL and Hive
I modified the package and created jira https://issues.apache.org/jira/browse/HIVE-11055. Thanks, Dmitry On Thu, Jun 18, 2015 at 4:26 PM, Dmitry Tolpeko dmtolp...@gmail.com wrote: 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 alanfga...@gmail.com 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 dmtolp...@gmail.com 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 alanfga...@gmail.com 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 dmtolp...@gmail.com 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 dmtolp...@gmail.com 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 alanfga...@gmail.com 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.
Re: PL/HQL and Hive
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 alanfga...@gmail.com 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 dmtolp...@gmail.com 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 alanfga...@gmail.com 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 dmtolp...@gmail.com 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 dmtolp...@gmail.com 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 alanfga...@gmail.com 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.
Re: PL/HQL and Hive
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 On Wed, Jun 17, 2015 at 9:55 PM, Alan Gates alanfga...@gmail.com wrote: 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 dmtolp...@gmail.com 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
Re: PL/HQL and Hive
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 mailto:dmtolp...@gmail.com 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
Re: PL/HQL and Hive
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 mailto:dmtolp...@gmail.com 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 mailto:alanfga...@gmail.com 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 mailto:dmtolp...@gmail.com 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 mailto:dmtolp...@gmail.com 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 mailto:alanfga...@gmail.com 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.
