[
https://issues.apache.org/jira/browse/CALCITE-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367750#comment-15367750
]
Josh Elser commented on CALCITE-1308:
-------------------------------------
bq. Phoenix implements DatabaseMetaData.getPrimaryKeys().
Yup, I have no reason to think that it's a Phoenix issue at this point.
bq. It sounds as if sqlline is doing the right thing given the information it
is getting, and Avatica is doing the right thing
Not entirely sure if this is true yet. I need to spend some more quality time
with a debugger. I just saw enough that the getPrimaryKeys call that sqlline
was making _looked_ correct but received no data. Need to dig some more.
> Primary Keys for Phoenix table not recognized in sqlline.
> ---------------------------------------------------------
>
> Key: CALCITE-1308
> URL: https://issues.apache.org/jira/browse/CALCITE-1308
> Project: Calcite
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Minor
> Fix For: avatica-1.9.0
>
>
> Noticed in CALCITE-1291: sqlline normally highlights the column(s) which are
> (part of the) primary key. Running a debugger over it quickly, showed that no
> keys were returned over the DatabaseMetaData.getPrimaryKeys call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
