Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 25 Sep 2012 14:00:09 +1100 (NCT)
From: "Lianhui Wang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <52508523.120273.1348542009140.JavaMail.jiratomcat@arcas>
In-Reply-To: <2146428847.87059.1347875227829.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HIVE-3472) Build An Analytical SQL Engine for
 MapReduce
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HIVE-3472?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13462=
391#comment-13462391 ]=20

Lianhui Wang commented on HIVE-3472:
------------------------------------

nexr have done some works in oracle sql to hive sql.
the session's address(from page 18):
http://www.slideshare.net/cloudera/hadoop-world-2011-replacing-rdbdw-with-h=
adoop-and-hive-for-telco-big-data-jason-han-nexr
i think we should transfer the oracle's syntax tree to hive's syntax tree.t=
hat maybe easy.
another thing is directly transfer the oracle's sql to hive query play.but =
i think that need more time and works.

               =20
> Build An Analytical SQL Engine for MapReduce
> --------------------------------------------
>
>                 Key: HIVE-3472
>                 URL: https://issues.apache.org/jira/browse/HIVE-3472
>             Project: Hive
>          Issue Type: New Feature
>    Affects Versions: 0.10.0
>            Reporter: Shengsheng Huang
>         Attachments: SQL-design.pdf
>
>
> While there are continuous efforts in extending Hive=E2=80=99s SQL suppor=
t (e.g., see some recent examples such as HIVE-2005 and HIVE-2810), many wi=
dely used SQL constructs are still not supported in HiveQL, such as selecti=
ng from multiple tables, subquery in WHERE clauses, etc. =20
> We propose to build a SQL-92 full compatible engine (for MapReduce based =
analytical query processing) as an extension to Hive.=20
> The SQL frontend will co-exist with the HiveQL frontend; consequently, on=
e can  mix SQL and HiveQL statements in their queries (switching between Hi=
veQL mode and SQL-92 mode using a =E2=80=9Chive.ql.mode=E2=80=9D parameter =
before each query statement). This way useful Hive extensions are still acc=
essible to users.=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira