phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1311) HBase namespaces surfaced in phoenix
Date Tue, 12 Apr 2016 14:50:25 GMT


ASF GitHub Bot commented on PHOENIX-1311:

Github user ankitsinghal commented on the pull request:
    @samarthjain , thanks for the review. 
    I'm unsure about disabling schema constructs if isNamespaceMapping is not enabled in config.
As this property is client side property and even if it is unset , user can still access the
table mapped to namespace created by another client which has this property set. This property
just ensure schema mapping to namespace during creation of table.
    I think these constructs still make sense independently. but @JamesRTaylor / @samarthjain
, if you guys think of disabling it , I'm ok with that too.

> HBase namespaces surfaced in phoenix
> ------------------------------------
>                 Key: PHOENIX-1311
>                 URL:
>             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

View raw message