You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "N Campbell (JIRA)" <ji...@apache.org> on 2017/01/25 03:10:28 UTC
[jira] [Created] (PHOENIX-3629) ambiguous table reference
N Campbell created PHOENIX-3629:
-----------------------------------
Summary: ambiguous table reference
Key: PHOENIX-3629
URL: https://issues.apache.org/jira/browse/PHOENIX-3629
Project: Phoenix
Issue Type: Bug
Environment: Hortonworks 2.5.3
Reporter: N Campbell
phoenix-4.7.0.2.5.3.0-37-client
The following statement should be parseable without having to add a correlation name to both tables (works in many other vendors).
select TJOIN1.RNUM, TJOIN1.C1, TJOIN1A.C1 from TJOIN1, TJOIN1 TJOIN1A where TJOIN1.C1=TJOIN1A.C1
Error -1 (00000) : Error while executing SQL "select TJOIN1.RNUM, TJOIN1.C1, TJOIN1A.C1 from TJOIN1, TJOIN1 TJOIN1A where TJOIN1.C1=TJOIN1A.C1": Remote driver error: RuntimeException: org.apache.phoenix.schema.AmbiguousTableException: ERROR 501 (42000): Table name exists in more than one table schema and is used without being qualified. -> AmbiguousTableException: ERROR 501 (42000): Table name exists in more than one table schema and is used without being qualified.
create table if not exists TJOIN1 (RNUM integer not null primary key , C1 integer, C2 integer);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)