phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3419) phoenix client (sqlline) adds a duplicate table schema to the query
Date Tue, 01 Nov 2016 18:43:58 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626291#comment-15626291
] 

James Taylor commented on PHOENIX-3419:
---------------------------------------

Please post your CREATE TABLE and CREATE INDEX statements, [~sgandotra]. Just a hunch, but
it sounds like your CREATE INDEX statement may be mistakenly using the schema name in the
index name when created. It should look something like this:
{{CREATE INDEX my_index_name ON ARCHIVE.FIELD_HISTORY_ARCHIVE  (...) }}

> phoenix client (sqlline) adds a duplicate table schema to the query
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-3419
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3419
>             Project: Phoenix
>          Issue Type: Bug
>         Environment: HBase 0.98.20
>            Reporter: Saurabh
>
> phoenix client (sqlline) adds a duplicate table schema to the query. This causes the
select query to fail with table not found exception. Other DDL operations also are failing.
This appears to occur only with tables which have a secondary index.
> describe still works correctly.
> 0: jdbc:phoenix:istbd4-mnds1-1-crd.eng.sfdc.n> select count(1) from archive.field_history_archive;
> Error: ERROR 1012 (42M03): Table undefined. tableName=ARCHIVE.ARCHIVE.FIELD_HISTORY_ARCHIVE
(state=42M03,code=1012)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message