impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Behm (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-4814) Frontend fails to analyze fully qualified table names where table name starts with numeric characters
Date Tue, 13 Jun 2017 00:42:00 GMT

     [ https://issues.apache.org/jira/browse/IMPALA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Behm resolved IMPALA-4814.
------------------------------------
    Resolution: Duplicate

Duplicates IMPALA-941

> Frontend fails to analyze fully qualified table names where table name starts with numeric
characters
> -----------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-4814
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4814
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 2.8.0
>            Reporter: Mostafa Mokhtar
>              Labels: ramp-up
>
> This works fine in hive.
> {code}
> hive> create table foo.3_ (c1 int);
> OK
> Time taken: 0.151 seconds
> hive>
> {code}
> Yet it fails in Impala. 
> Repro 
> {code}
> create table many_files.2_ (c1 int) ;
> {code}
> Error
> {code}
> create table many_files.3_ (c1 int)
>                        ^
> Encountered: DECIMAL LITERAL
> Expected: ADD, AND, ARRAY, AS, ASC, BETWEEN, BIGINT, BINARY, BLOCK_SIZE, BOOLEAN, CACHED,
CASCADE, CHANGE, CHAR, COMMENT, COMPRESSION, CROSS, DATE, DATETIME, DECIMAL, DEFAULT, DESC,
DIV, REAL, DROP, ELSE, ENCODING, END, FLOAT, FOLLOWING, FROM, FULL, GROUP, IGNORE, HAVING,
ILIKE, IN, INNER, INTEGER, IREGEXP, IS, JOIN, LEFT, LIKE, LIMIT, LOCATION, MAP, NOT, NULL,
NULLS, OFFSET, ON, OR, ORDER, PARTITION, PARTITIONED, PRECEDING, PRIMARY, PURGE, RANGE, RECOVER,
REGEXP, RENAME, REPLACE, RESTRICT, RIGHT, RLIKE, ROW, ROWS, SELECT, SET, SMALLINT, STORED,
STRAIGHT_JOIN, STRING, STRUCT, TBLPROPERTIES, THEN, TIMESTAMP, TINYINT, TO, UNCACHED, UNION,
USING, VALUES, VARCHAR, WHEN, WHERE, WITH, COMMA, IDENTIFIER
> CAUSED BY: Exception: Syntax error
> {code}
> Exception
> {code}
> 	at org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:424)
> 	at org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:363)
> 	at org.apache.impala.service.Frontend.analyzeStmt(Frontend.java:894)
> 	at org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1034)
> 	at org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:159)
> Caused by: java.lang.Exception: Syntax error
> 	at org.apache.impala.analysis.SqlParser.unrecovered_syntax_error(SqlParser.java:1314)
> 	at java_cup.runtime.lr_parser.parse(lr_parser.java:619)
> 	at org.apache.impala.analysis.AnalysisContext.analyze(AnalysisContext.java:378)
> 	... 4 more
> I0124 11:08:29.581303 137846 status.cc:114] AnalysisException: Syntax error in line 1:
> create table many_files.3_ (c1 int)
> {code}
> Querying for the same use case also fails
> {code}
> Query: explain select count(*) from many_files.2_
> ERROR: AnalysisException: Syntax error in line 1:
> explain select count(*) from many_files.2_
>                                        ^
> Encountered: DECIMAL LITERAL
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message