[
https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129278#comment-15129278
]
Enis Soztutar commented on PHOENIX-1311:
----------------------------------------
bq. We could then have a MR-based conversion tool to migrate the existing data
of a table into a namespace aware Phoenix table
If there is no data layout change, but only hbase table name change, the best
way would be to take snapshot then restore snapshot as a table in the desired
namespace.
We may also need to find a way to auto-create the namespaces in HBase for
existing schemas in Phoenix. Agreed that a short design doc talking about how
the end state would be good.
> 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)
