[
https://issues.apache.org/jira/browse/HAWQ-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287901#comment-15287901
]
Michael Andre Pearce (IG) edited comment on HAWQ-393 at 5/17/16 11:48 PM:
--------------------------------------------------------------------------
Unfortunately not, just been checking tableau desktop and all documents the
custom sql is not for the schema and table self discovery. But simply creating
a custom access to a database table such as what i can already do to make
access to hcatalog tables using SELECT * FROM hcatalog.myschema.mytable but
isn't great for the general end user.
https://onlinehelp.tableau.com/current/pro/online/mac/en-us/customsql.html
Tableau define quite clearly the contract (which i happen to agree with) is at
the ODBC layer, this is indeed the purpose of ODBC,
http://kb.tableau.com/articles/knowledgebase/tableau-and-odbc
as such either this needs to be:
masked away down in the server to keep compatibility with current postgres
drivers / data direct drivers.
or
hawq needs to make and maintain a custom client also for ODBC for the above
feature and other bits needed.
I would propose the former and keep this logic out the client but in the server
and map it there, as then keeps compatibility with your existing odbc drivers
and other clients and avoids you needing to maintain ODBC drivers and these
features.
was (Author: michael.andre.pearce):
Unfortunately not, just been checking tableau desktop and all documents the
custom sql is not for the schema and table self discovery. But simply creating
a custom access to a database such as what i can already do but isn't great for
the general end user.
https://onlinehelp.tableau.com/current/pro/online/mac/en-us/customsql.html
Tableau define quite clearly the contract (which i happen to agree with) is at
the ODBC layer, this is indeed the purpose of ODBC,
http://kb.tableau.com/articles/knowledgebase/tableau-and-odbc
as such either this needs to be:
masked away down in the server to keep compatibility with current postgres
drivers / data direct drivers.
or
hawq needs to make and maintain a custom client also for ODBC for the above
feature and other bits needed.
I would propose the former and keep this logic out the client but in the server
and map it there, as then keeps compatibility with your existing odbc drivers
and other clients and avoids you needing to maintain ODBC drivers and these
features.
> 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)
