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 Fri, 08 Apr 2016 08:08:25 GMT


ASF GitHub Bot commented on PHOENIX-1311:

Github user ankitsinghal commented on a diff in the pull request:
    --- Diff: phoenix-core/src/main/java/org/apache/hadoop/hbase/ipc/controller/
    @@ -36,7 +37,16 @@
    -			.add(PhoenixDatabaseMetaData.SYSTEM_FUNCTION_NAME).build();
    +			.add(PhoenixDatabaseMetaData.SYSTEM_FUNCTION_NAME)
    +            .add(SchemaUtil.getPhysicalTableName(PhoenixDatabaseMetaData.SYSTEM_CATALOG_NAME_BYTES,
    --- End diff --
    yeah, namespace mapping for system tables will not always be true as it is controlled
with phoenix.connection.mapSystemTablesToNamespace, 
    but this is just the list of system tables, so it includes SYSTEM.CATAOG and SYSTEM:CATALOG
both to set the priority for RPC accordingly. 
    do you think, it could have any impact?

> 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