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

Saurabh commented on PHOENIX-3419:
----------------------------------

[~giacomotaylor] [~jamestaylor] - sorry for the delay, here is the DDL for the 
index

CREATE INDEX IF NOT EXISTS FIELD_HISTORY_ARCHIVE_INDEX 
ON ARCHIVE.FIELD_HISTORY_ARCHIVE (PARENT_KEY_PREFIX, CREATED_DATE, PARENT_ID, 
ENTITY_HISTORY_ID)
INCLUDE 
   (FIELD_HISTORY_ARCHIVE_ID, CREATED_BY_ID, FIELD, DATA_TYPE, OLDVAL_STRING, 
NEWVAL_STRING, 
   OLDVAL_FIRST_NAME, NEWVAL_FIRST_NAME, OLDVAL_LAST_NAME, NEWVAL_LAST_NAME, 
OLDVAL_NUMBER,
    NEWVAL_NUMBER, OLDVAL_DATE, NEWVAL_DATE, ARCHIVE_PARENT_TYPE, 
ARCHIVE_FIELD_NAME,
    ARCHIVE_TIMESTAMP, ARCHIVE_PARENT_NAME, DIVISION, CONNECTION_ID) ASYNC

> 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)

Reply via email to