[
https://issues.apache.org/jira/browse/HIVE-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474838#comment-13474838
]
Shengsheng Huang commented on HIVE-3472:
----------------------------------------
@Lianhui Thanks for comment. I read the nexr's slides. And there's another
interesting contribution about SQL window functions presented in Hadoop Summit
2012. http://www.slideshare.net/Hadoop_Summit/analytical-queries-with-hive.
It looks to me many people are aware that Hive needs improvement to better
accomodate commmon OLAP requirements, and many of us actually share similar
ideas about which areas to improve - for example, the SQL data type system,
OLAP-oriented features (rank,rollup,window functions,etc.), nested & scalar
subquery, and etc.
It seemed nexr didn't open source their query planer (Hawk), which does the
most SQL syntax transformation as I understand, on github (they did contributed
a set of OLAP UDF implementations though). We would like to see Hive evolves
faster to a better open source tool for OLAP analytics so that we opened this
JIRA id to push this forward. And we're willing to contribute our efforts to
open source.
> 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
