[
https://issues.jboss.org/browse/TEIIDDES-2094?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2094:
----------------------------------------
Now that we can get Property Definitions from the API... not sure what to do with that
data. I see you are defining these properties view java @annotation attributes.
The application of extension properties to EMF (tags referencing actual objects) objects
is pretty straight forward, but there also has to be some mapping between the Teiid
property definitions and their target EMF object types.
* The extension properties coming from the Teiid runtime define *owner* objects like:
*org.teiid.metadata.Column*
* In Designer, these relational objects are defined differently:
*org.teiid.designer.metamodels.relational.impl.ColumnImpl*
However, without persisting the entire set of property definitions (either in the model on
in the Designer workspace) it'd be impossible to re-edit a model and change the
extension property values. There has to be a "schema- like- definition somewhere (aka
MED) that is the frame of reference to make this possible.
So Designer options would be to create another type of MED OR somehow convert the runtime
ext. properties into a MED.
Seems to me that we're bookkeeping extension properties using 2 methodologies and ...
that we're missing something here in our design(s).
Support for dynamic extension metadata
---------------------------------------
Key: TEIIDDES-2094
URL:
https://issues.jboss.org/browse/TEIIDDES-2094
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Reporter: Ramesh Reddy
Priority: Critical
Currently when Teiid core implements a new translator or customer/user implements a
custom translator that has extension metadata, before they can use the translator in
Designer to do some modeling, they need to define MED and register it.
With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to
interrogate the extension metadata properties defined for a translator.
Currently if user uses Teiid Connection importer with any new translator, it ignores all
the extension metadata properties and removes them from the returned DDL that Designer did
not recognize. That is really bad for custom connectors, because the VDB will not work
properly once it is deployed back to Teiid Server.
I propose to devise a way to generate a dynamic MED for the purposes of current metadata
import of the source and use it during the import and not ignore those extension metadata
properties.
Depending upon implementation detail, we can also read the translators and their
extension metadata support during the initial connection time and create all the required
MEDs and register them.
--
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