[
https://issues.apache.org/jira/browse/HIVE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354996#comment-14354996
]
Ron de Bruijn commented on HIVE-94:
-----------------------------------
It would be nice if there would be an actual grammar specification somewhere,
with an intended semantics in a different document; preferably an operational
or denotational semantics.
The link above points at a document which doesn't specify how a select_expr can
be constructed in the general case.
> re-factor Hive grammar to be more human readable
> ------------------------------------------------
>
> Key: HIVE-94
> URL: https://issues.apache.org/jira/browse/HIVE-94
> Project: Hive
> Issue Type: Improvement
> Components: Documentation, Query Processor
> Reporter: Pete Wyckoff
>
> Hive.g grammar specification could be re-factored to look more friendly.
> MySQL's select statement looks like this on the docs page and presumably,
> their grammar is similar.
> {noformat}
> SELECT
> [ALL | DISTINCT | DISTINCTROW ]
> [HIGH_PRIORITY]
> [STRAIGHT_JOIN]
> [SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT]
> [SQL_CACHE | SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS]
> select_expr, ...
> [FROM table_references
> [WHERE where_condition]
> [GROUP BY {col_name | expr | position}
> [ASC | DESC], ... [WITH ROLLUP]]
> [HAVING where_condition]
> [ORDER BY {col_name | expr | position}
> [ASC | DESC], ...]
> [LIMIT {[offset,] row_count | row_count OFFSET offset}]
> [PROCEDURE procedure_name(argument_list)]
> [INTO OUTFILE 'file_name' export_options
> | INTO DUMPFILE 'file_name'
> | INTO var_name [, var_name]]
> [FOR UPDATE | LOCK IN SHARE MODE]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
