hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-824) SQL interface for Pig
Date Tue, 04 May 2010 21:29:07 GMT

     [ https://issues.apache.org/jira/browse/PIG-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thejas M Nair updated PIG-824:
------------------------------

    Attachment: pigsql.patch
                pig_sql_beta.pdf
                java-cup-11a-runtime.jar

 SQL patch (pigsql.patch) based on version of owl in svn  and documentation (pig_sql_beta.pdf).
 Patch is against the trunk revision 941018 .


> SQL interface for Pig
> ---------------------
>
>                 Key: PIG-824
>                 URL: https://issues.apache.org/jira/browse/PIG-824
>             Project: Pig
>          Issue Type: New Feature
>            Reporter: Olga Natkovich
>         Attachments: java-cup-11a-runtime.jar, PIG-824.1.patch, PIG-824.binfiles.tar.gz,
pig_sql_beta.pdf, pigsql.patch, SQL_IN_PIG.html
>
>
> In the last 18 month PigLatin has gained significant popularity within the open source
community. Many users like its data flow model, its rich type system and its ability to work
with any data available on HDFS or outside. We have also heard from many users that having
Pig speak SQL would bring many more users. Having a single system that exports multiple interfaces
is a big advantage as it guarantees consistent semantics, custom code reuse, and reduces the
amount of maintenance. This is especially relevant for project where using both interfaces
for different parts of the system is relevant.  For instance, in a 
> data warehousing system, you would have ETL component that brings data  into the warehouse
and a component that analyzes the data and produces reports. PigLatin is uniquely suited for
ETL processing while SQL might be a better fit for report generation.
> To start, it would make sense to implement a subset of SQL92 standard and to be as much
as possible standard compliant. This would include all the standard constructs: select, from,
where, group-by + having, order by, limit, join (inner + outer). Several extensions  such
as support for pig's UDFs and possibly streaming, multiquery and support for pig's complex
types would be helpful.
> This work is dependent on metadata support outlined in https://issues.apache.org/jira/browse/PIG-823

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message