[
https://issues.jboss.org/browse/TEIID-2982?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2982:
---------------------------------------
It looks like we'll have to change where/how we store the visibility flag to make this
possible. From a metadata perspective we can go one of two ways:
Reuse the existing model element -
{code}<model name="x" type="IMPORTED"
visible="false">{code}
This would probably be the direction if we envision even more complicated override
scenarios.
Add the info to the import with a stripped down model element -
{code}<import-vdb name="foo" version="1"><model
name="x" visible="false"></import-vdb>{code}
Allow to change visibility to a model from imported vdb
-------------------------------------------------------
Key: TEIID-2982
URL:
https://issues.jboss.org/browse/TEIID-2982
Project: Teiid
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 8.7
Reporter: Kenichi Takemura
Assignee: Steven Hawkins
When a new vdb uses import-vdb, changing(override) visibility to a model from imported
vdb would need to hide non-related model to the new vdb.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)