[
https://jira.jboss.org/jira/browse/TEIID-685?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-685:
--------------------------------------
Directly exposed metadatarecord objects to the connector api that can be created through a
MetadataFactory (that hides most of the wiring logic related to index files). The initial
check-in supports creating tables and columns, the next target adds keys, indexes,
annotations, and extension properties. The final will add procedures.
There is still a discussion over whether to bother hiding these impl object behind an
interface - or even expanding the existing group, element, etc. interfaces. My view would
be that this is an expert api in 6.x and we shouldn't spend too much time trying to
protect users from themselves.
In 7.x an effort should be made to clean up not only the api, but the system tables, since
they are intrinsically tied to many of the "index" concepts and the present form
of the metadata record objects.
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