[
https://jira.jboss.org/jira/browse/TEIID-685?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-685:
------------------------------------
Ideally I would like to see one consistent Metadata API defined in the Connector API. I do
not think I have preference either way to define the interfaces in the current recordImpl
objects or extend the group, element. I probably vote for the former, as that moves into
the notion of tables and columns instead of the previous metamatrix notion of groups and
elements.
Define Metadata aware Connector API
-----------------------------------
Key: TEIID-685
URL:
https://jira.jboss.org/jira/browse/TEIID-685
Project: Teiid
Issue Type: Sub-task
Components: Connector API
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Priority: Critical
Fix For: 6.2.0
Connector API needs to be extended, such that a connector can selectively implement an
interface with which it can expose the metadata of the connector. This is similar to the
concept of JDBC drivers exposing the metadata of the sources they are connected to.
At a minimum, this API must expose all the available
- Tables, with corresponding elements
- Procedures with corresponding parameters
in the data source. There should also be a way to define user defined properties on all
the objects, that can used by tools as they fit.
Please comment, if there are any specific features you would like this to extend, as PK,
FK, Unique keys, indexes etc. Overtime, it is expectation that this will be grown to full
blown metadata store API as the teiid-metadata project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira