[
https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2476:
---------------------------------------
BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1609306
A question brought up on the BZ was about the visibility of schema entries - yes that is a
known limitation of this initial implementation. The basic problem is highlighted by the
code comment:
//TODO - schemas cannot be hidden - unless we traverse them and find that nothing is
accessible
That is you can have no general access to a schema, but turn on access to a particular
table. In which case we cannot omit the schema from the metadata. So at worst you are
leaking the names of all of the schema in the vdb. An issue can be opened on this if
needed.
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
Priority: Major
Fix For: 9.0, 8.12.15.6_4
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
(v7.12.1#712002)