hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Tolpeko <dmtolp...@gmail.com>
Subject Re: PL/HQL - Procedural SQL-on-Hadoop
Date Tue, 03 Mar 2015 06:18:55 GMT
Venkat,

The goal of this project is to execute existing PL/SQL in Hive as much as
possible, not to migrate. In case when some design restrictions are faced
the code has to be redesigned, but hopefully most of the remaining code
remained untouched, no need to convert everything to bash/Python etc.

Dmitry

On Tue, Mar 3, 2015 at 4:39 AM, Venkat, Ankam <Ankam.Venkat@centurylink.com>
wrote:

>  Is there a simple way to migrate from PL/SQL to PL/HQL?
>
>
>
> Regards,
>
> Venkat
>
>
>
> *From:* Dmitry Tolpeko [mailto:dmtolpeko@gmail.com]
> *Sent:* Friday, February 27, 2015 1:36 PM
> *To:* user@hive.apache.org
> *Subject:* PL/HQL - Procedural SQL-on-Hadoop
>
>
>
> Let me introduce PL/HQL, an open source tool that implements procedural
> SQL on Hadoop. It is going to support all major procedural syntaxes. The
> tool can be used with any SQL-on-Hadoop solution.
>
>
>
> Motivation:
>
>    - Writing the driver code using well-known procedural SQL (not bash)
>    that enables Hadoop to even more wider audience
>    - Allowing dynamic SQL, iterations, flow-of-control and SQL exception
>    handling
>    - Facilitating migration of RDBMS workload to Hadoop
>
>  Plans (besides extending syntax):
>
>
>
>    - Supporting CREATE PROCEDURE/FUNCTION/PACKAGE to reuse code
>    - Allowing connections to multiple databases (i.e. lookup tables in
>    relational databases)
>    - On-the-fly SQL conversion (SELECT i.e.), compatibility layers
>
>  More details can be found at http://www.plhql.org/
>
>
>
> It is just the first release PL/HQL 0.01 to show that such project exists
> and get any initial feedback.
>
>
>
> Thank you,
>
>
>
> Dmitry Tolpeko
>   This communication is the property of CenturyLink and may contain
> confidential or privileged information. Unauthorized use of this
> communication is strictly prohibited and may be unlawful. If you have
> received this communication in error, please immediately notify the sender
> by reply e-mail and destroy all copies of the communication and any
> attachments.
>

Mime
View raw message