[
https://issues.apache.org/jira/browse/PHOENIX-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628111#comment-15628111
]
Samarth Jain commented on PHOENIX-3419:
---------------------------------------
Looks like a similar issue was fixed in
https://issues.apache.org/jira/browse/PHOENIX-3307
> 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)