[
https://issues.apache.org/jira/browse/HIVE-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475080#comment-13475080
]
alex gemini commented on HIVE-3472:
-----------------------------------
It's seems there're two unrelated issues we discussed here,one for analytic
function,one for compatible for sql-92.
for analytic features,I think it's OK to built a new parser since there is no
standard,special vendor has some special grammar, we can just treat it like a
new framework with a parameter to control whether enable it or not,just like
HIVE-896 did, we open a new session with special shell command,new feature with
lots of code integration into hive is always change many thing like
metastore,execution engine,explain tree etc. I guess it's ok to have a
parameter switch. But why we are using pl/sql parser, what exactly analytical
features we're talking about? for sql-92 compatible issue we should discussed
in HIVE-3561.
> 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’s SQL support (e.g., see
> some recent examples such as HIVE-2005 and HIVE-2810), many widely used SQL
> constructs are still not supported in HiveQL, such as selecting from multiple
> tables, subquery in WHERE clauses, etc.
> We propose to build a SQL-92 full compatible engine (for MapReduce based
> analytical query processing) as an extension to Hive.
> The SQL frontend will co-exist with the HiveQL frontend; consequently, one
> can mix SQL and HiveQL statements in their queries (switching between HiveQL
> mode and SQL-92 mode using a “hive.ql.mode” parameter before each query
> statement). This way useful Hive extensions are still accessible to users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
