[teiid-issues] [JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164663#comment-13164663 ] 

Steven Hawkins commented on TEIID-2476:
---------------------------------------

>  I know that is separate from this issue, but I can log that.

If you hide the system tables, then DatabaseMetaData, ODBC metadata (which is needed even for just query execution), and even some geospatial logic won't work.  So allowing them to be hidden would be a somewhat extreme case.

> As per this issue, if we implement at DatabaseMetadata does't that differ with System metadata?

DatabaseMetaData uses queries and some additional logic against the system metadata.  I'm just saying that working this at the DatabaseMetaData layer is simpler.  For consistency we'll have to implement this at the system table level and redo any of the materialization above.

> Exclude hidden tables/columns from metadata
> -------------------------------------------
>
>                 Key: TEIID-2476
>                 URL: https://issues.jboss.org/browse/TEIID-2476
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: JDBC Driver, Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 9.0
>
>
> We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata.  This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)