[
https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185118#comment-15185118
]
James Taylor commented on PHOENIX-1311:
---------------------------------------
I like the idea of having this just impact the physical name we store, but I
think there may be corner cases. Also, the CREATE TABLE case may be tricky, as
we create the metadata before we really have a PTable. I think it'd be ok to
have a global client-side config that enables/disables this functionality (or
alternatively, it's always on, but we force an upgrade prior to usage).
One more minor nit: rather than a version flag on the SYSTEM.CATALOG table, we
typically have a boolean indicator specific to the feature on whether it's
enabled or not.
> 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_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)
