4:54 a.m.
Ramesh Reddy created TEIID-1971:
-----------------------------------
Summary: Provide delegating Metadata Repository implementation class
Key: TEIID-1971
URL: https://issues.jboss.org/browse/TEIID-1971
Project: Teiid
Issue Type: Task
Components: Connector API
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
The Metadata Repository is interface defined to import metadata from variety of sources.
It is useful to provide a base implementation of of delegating metadata repository such
that it can be overridden by users to provide their own implementations, on top of already
already available methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 a.m.
[
https://issues.jboss.org/browse/TEIID-1971?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-1971.
---------------------------------
Resolution: Done
Instead of delegation model, I have created a stack/list model where multiple
MetadataRepositories can be concatenated to share responsiblity to load the metadata of
the given model.
This can be acived by providing a comma separated list of import types for ex:
{code:XML|title=Sample vdb.xml file}
<vdb name="{vdb-name}" version="1">
<model name="{model-name}" type="PHYSICAL">
<source name="AccountsDB" translator-name="oracle"
connection-jndi-name="java:/oracleDS"/>
<metadata type="NATIVE,DDL">
**DDL Here**
</metadata>
</model>
</vdb>
{code}
For the above model, _NATIVE_ importer is first used, then DDL importer used to add
additional metadata to _NATIVE_ imported metadata. It can also take custom module name as
the metadata repo names
See the User Defined Functions in Developer's guide for possible use cases.
Provide delegating Metadata Repository implementation class
-----------------------------------------------------------
Key: TEIID-1971
URL: https://issues.jboss.org/browse/TEIID-1971
Project: Teiid
Issue Type: Task
Components: Connector API
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
The Metadata Repository is interface defined to import metadata from variety of sources.
It is useful to provide a base implementation of of delegating metadata repository such
that it can be overridden by users to provide their own implementations, on top of already
already available methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 p.m.
[
https://issues.jboss.org/browse/TEIID-1971?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1971.
---------------------------------
Provide delegating Metadata Repository implementation class
-----------------------------------------------------------
Key: TEIID-1971
URL: https://issues.jboss.org/browse/TEIID-1971
Project: Teiid
Issue Type: Task
Components: Connector API
Affects Versions: 8.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.0
The Metadata Repository is interface defined to import metadata from variety of sources.
It is useful to provide a base implementation of of delegating metadata repository such
that it can be overridden by users to provide their own implementations, on top of already
already available methods.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4195
days inactive
4447
days old
2 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Steven Hawkins (JIRA)