[
https://issues.jboss.org/browse/TEIID-5753?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5753:
---------------------------------------
The most general solution is to add the visible flag to schema objects as well. However
there are quite a few changes that are needed for that - teiid system metadata, odata
metadata, even places in pg metadata.
Alternatively a grant based approach would be an exception to the deny all assumption -
that is there is an implicit permission in odata that makes stuff visible and you have to
issue an explicit deny to remove it.
The final approach is extension metadata specific to the odata interface - which is the
most informal.
I'm not quite sure yet which of these makes the most sense.
Please add extension metadata support to allow for an invisibility
option on single foreign tables/views for odata layer
------------------------------------------------------------------------------------------------------------------------
Key: TEIID-5753
URL:
https://issues.jboss.org/browse/TEIID-5753
Project: Teiid
Issue Type: Enhancement
Components: OData
Reporter: Christoph John
Assignee: Steven Hawkins
Priority: Major
Fix For: 13.0
The issue arose from the discussion at
https://developer.jboss.org/message/989502#989502
> Every tables and view I specify is becoming visible in the odata service. Of course
I can use GRANT to resctrict access, however, it would be more nice to not export the
tables in the odata layer in the first place. Would it be possible to add some kind of per
table/view INVISIBLE OPTION for odata, or could I reach the same result in a different way
and how would this look like?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)