[
https://issues.apache.org/jira/browse/IMPALA-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490444#comment-16490444
]
abipc commented on IMPALA-941:
------------------------------
[~jbapple] Looked at the [SQL
standard|[http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt],] an
identifier must not start with number. Refer to page 85 in the above document
(this is slightly outdated, cannot get reference to latest one)
Should we still allow this in Impala. Impala already supports quoted names.
> Impala Parser issue when using fully qualified table names that start with a
> number.
> ------------------------------------------------------------------------------------
>
> Key: IMPALA-941
> URL: https://issues.apache.org/jira/browse/IMPALA-941
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 1.2.4
> Reporter: Udai Kiran Potluri
> Assignee: abipc
> Priority: Minor
> Labels: customer, newbie
>
> Impala Parser issue when using fully qualified table names that start with a
> number.
> What is going wrong is that Impala is parsing the table name as a floating
> point literal since the text starts with a number and contains a period.
> {code}
> INVALIDATE METADATA db.571_market;
> Query: invalidate METADATA db.571_market
> ERROR: AnalysisException: Syntax error in line 1:
> invalidate METADATA db.571_market
> ^
> Encountered: FLOATING POINT LITERAL
> Expected: ADD, AS, CHANGE, COMMENT, CROSS, DROP, FULL, GROUP, HAVING, INNER,
> JOIN, LEFT, LIKE, LIMIT, LOCATION, ON, ORDER, PARTITION, RENAME, REPLACE,
> RIGHT, ROW, SELECT, SET, STORED, TBLPROPERTIES, UNION, USING, VALUES, WHERE,
> WITH, COMMA, IDENTIFIER
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
