You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2016/01/05 22:09:39 UTC

[jira] [Resolved] (PHOENIX-2523) Use same client/server caching mechanism for Phoenix/Calcite

     [ https://issues.apache.org/jira/browse/PHOENIX-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maryann Xue resolved PHOENIX-2523.
----------------------------------
    Resolution: Fixed

> Use same client/server caching mechanism for Phoenix/Calcite
> ------------------------------------------------------------
>
>                 Key: PHOENIX-2523
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2523
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Maryann Xue
>              Labels: calcite
>
> Rather than query through the DatabaseMetaData APIs, Phoenix/Calcite should use the same client/server caching mechanism as standalone Phoenix. One challenge is that Calcite looks at the schema first and then at the tables under that schema (one level at a time), while Phoenix doesn't have a physical representation of a schema. Instead, it resolves a table given the schema name and table name together. One solution may be to never give an error in Phoenix/Calcite when a schema level is traversed, but only actually resolve when the next level is traversed.



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