You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/07/18 05:29:00 UTC
[jira] [Commented] (PHOENIX-4035) Consider tables and sequences
under same namespace in Phoenix-Calcite
[ https://issues.apache.org/jira/browse/PHOENIX-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091133#comment-16091133 ]
Julian Hyde commented on PHOENIX-4035:
--------------------------------------
bq. And at the same time Calcite expects table names also should not match with schema names so we should not allow creating tables with existing schema names as well.
I don't think that's true. If you have schemas "scott" and "foodmart", you can certainly have a table in "foodmart" schema called "scott". You can't have a sub-schema "emp" in "scott" if the "scott" schema also has a table called "emp" (just as you can't have a file and a directory with the same name in the same directory) but I don't think that is a problem for phoenix.
> Consider tables and sequences under same namespace in Phoenix-Calcite
> ---------------------------------------------------------------------
>
> Key: PHOENIX-4035
> URL: https://issues.apache.org/jira/browse/PHOENIX-4035
> Project: Phoenix
> Issue Type: Bug
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Labels: calcite, calcite-compat-change
>
> Currently tables and sequences are different namespaces so there can be sequences with table names or vice versa but in calcite sequences are resolved as tables so it's very difficult to distinguish them when the names are same. Physically we can have different tables for both sequences and tables but if we don't allow to create sequences or tables with existing names.
> And at the same time Calcite expects table names also should not match with schema names so we should not allow creating tables with existing schema names as well.
> FYI [~jamestaylor] [~julianhyde] [~ankit@apache.org].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)