[
https://issues.jboss.org/browse/TEIIDDES-2080?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2080:
----------------------------------------
Now that we can get Property Definitions from the API... not sure what to do with that
data.
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 property
definitions and their target EMF object types.
* The extension properties coming from the 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.
In order for these property definitions to be exposed by Teiid runtime, they have to be
defined statically somewhere in Teiid. Still don't know why a MED can't be used in
Teiiid and Designer?
Add Excel Datasource Extension metadata properties
--------------------------------------------------
Key: TEIIDDES-2080
URL:
https://issues.jboss.org/browse/TEIIDDES-2080
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Reporter: Ramesh Reddy
Fix For: 8.5
Teiid 8.7 introducing Excel translator which is based on Apache POI
https://issues.jboss.org/browse/TEIID-965. This translator defines some extension metadata
for it to works correctly in Teiid Designer. See this document as to what are the
properties and the name space and alias
https://docs.jboss.org/author/display/TEIID/Microsoft+Excel+Translator
--
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