[
https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173935#comment-15173935
]
James Taylor commented on PHOENIX-1311:
---------------------------------------
The backward compatibility case. let's assume you have a table {{FOO.BAR}} and
the query:
{code}
SELECT * FROM FOO.BAR;
{code}
The table would be in the empty HBase namespace today. We attempt to resolve
this to an HTable with the name "FOO.BAR" on the client side
(ConnectionQueryServices.getTable()), but instead now we'd resolve it as
"FOO:BAR". What will tell the client which way we should resolve it?
> 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)
