[
https://issues.apache.org/jira/browse/HAWQ-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287947#comment-15287947
]
Goden Yao commented on HAWQ-393:
--------------------------------
I see. What do you mean "masked away" - do you mean server should not show
"hcatalog" in database list? this might require some tricky logic and I
certainly don't want to manipulate pg_class and other catalog tables for that.
That's why we only implement the logic in HAWQ client to invoke the store proc.
> HAWQ access of hcatalog metadata using \d
> -----------------------------------------
>
> Key: HAWQ-393
> URL: https://issues.apache.org/jira/browse/HAWQ-393
> Project: Apache HAWQ
> Issue Type: New Feature
> Components: Hcatalog, PXF
> Reporter: Goden Yao
> Assignee: Oleksandr Diachenko
> Fix For: 2.0.0
>
>
> As a Hawq user, after enabling hcatalog integration feature,
> I want to be able to display (\d) tables in hcatalog so that I know what
> tables are available and the contents of their schemas.
> *Acceptance Criteria*
> 1. Ability to describe a single table.
> {code}
> \d hcatalog.databaseName.t1
> {code},
> {code}
> \d+ hcatalog.databaseName.t1
> {code}
> 2. Ability to describe the every table in a database of hcatalog:
> {code}
> \d hcatalog.databaseName.*
> {code}
> 3. Ability to list tables that match patterns (only wildcard is supported)
> e.g.
> {code}
> \d hcatalog.databaseName.prefix_*
> {code}
> 4. Ability to list databases in hcatalog:
> {code}
> \d hcatalog.*
> {code}
> 5. Tab autocomplete of items from hcatalog. (optional)
> [1] based on current implementation, we cache the meta data from hcatalog
> within the same transaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
