[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207918#comment-15207918 ]
ASF GitHub Bot commented on PHOENIX-1311: ----------------------------------------- Github user JamesRTaylor commented on the pull request: https://github.com/apache/phoenix/pull/153#issuecomment-200194873 Thanks for spinning up a pull request, @ankitsinghal. One functional question: how are you handling the case of a VIEW having a different schema name than it's base/physical table? Since the rows of a view are in the same physical table as the base table, they cannot be in different namespaces, correct? Please review, @samarthjain. > HBase namespaces surfaced in phoenix > ------------------------------------ > > Key: PHOENIX-1311 > URL: https://issues.apache.org/jira/browse/PHOENIX-1311 > Project: Phoenix > Issue Type: New Feature > Reporter: nicolas maillard > Assignee: Ankit Singhal > Priority: Minor > Fix For: 4.8.0 > > Attachments: PHOENIX-1311.docx, PHOENIX-1311_v1.patch, > PHOENIX-1311_v2.patch, PHOENIX-1311_wip.patch, PHOENIX-1311_wip_2.patch > > > Hbase (HBASE-8015) has the concept of namespaces in the form of > myNamespace:MyTable it would be great if Phoenix leveraged this feature to > give a database like feature on top of the table. > Maybe to stay close to Hbase it could also be a create DB:Table... > or DB.Table which is a more standard annotation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)