phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1311) HBase namespaces surfaced in phoenix
Date Mon, 29 Feb 2016 08:14:18 GMT


James Taylor commented on PHOENIX-1311:

Thanks for the design doc, [~ankit.singhal]. A couple of questions/comments:
-  I don't think we need to support {{SELECT SCHEMA()}} or {{SHOW SCHEMAS}} as there's a standard
JDBC method in DatabaseMetaData that would return the list of schemas. Plus we don't have
that kind of thing for tables. We could start introducing stuff like that (or we could leave
it to the tooling), but if we are going to introduce that, let's do it in a separate JIRA.
- Would you mind providing a couple of examples in SELECT queries for how the schema would
be used and resolved? You're not proposing using a different SELECT * FROM my_schema:my_table
syntax are you?
- For b/w compat, I'm not sure a version flag on PTable is enough. We need something outside
of this, as this will change the way we find the PTable in the first place. How do we know
how to look for it, as we currently look for an HTable with a name of "MY_SCHEMA.MY_TABLE".
Perhaps a global config on whether this feature is on or off, plus a requirement that the
upgrade is done if it's turned on?

> 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_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