[
https://issues.apache.org/jira/browse/HAWQ-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289313#comment-15289313
]
Goden Yao commented on HAWQ-393:
--------------------------------
Like I said, server side integration is risky at the moment. So we intend to
not modify system catalog for this.
For other clients , after they connect to HAWQ, can use store proc to get the
hcatalog schema info.
It's not ideal but it's the compromise we have to take right now.
For developer experience, as integrating 2 catalog info in one database is not
something in our original goals.
As I'm not familiar with Tableau, it'd be good if we can connect and you show
me a live demo or something?
> 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)
