[
https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123662#comment-15123662
]
Ankit Singhal commented on PHOENIX-1311:
----------------------------------------
[~jamestaylor], can you please review the approach(wip_2 patch):-
* we can take one flag (isUsingDefaultNamespace or something) for tables in
meta table which will differentiate the tables created with default namespace
even if they have schema associated with namespace mapped tables. This will
help in b/w compat.
* And for system.catalog table , we can either upgrade it to use always
namespace or we can check if table present in system namespace and fallback to
default if not.
* Need to see how we can handle local indexes and views as they have prefix
appended to the parent table(prefix_schema.table). should we map this to
schema.perfix_table not sure if it can impact the existing customers.
* We can use same approach in bulkload tools as well.
> 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_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)
