[JBoss JIRA] (TEIIDDES-2080) Add Excel Datasource Extension metadata properties
by Barry LaFond (JIRA)
[ 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
10 years, 2 months
[JBoss JIRA] (TEIIDDES-2033) Need to provide all system functions (i.e, aggregates) that user can use
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2033?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2033.
------------------------------------
Resolution: Done
Tested with Teiid 8.7 CR2. System functions were showing up and usable in T-editor's Function builder/wizard.
> Need to provide all system functions (i.e, aggregates) that user can use
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-2033
> URL: https://issues.jboss.org/browse/TEIIDDES-2033
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, Teiid Integration, Transformations
> Affects Versions: 8.3.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> The designer should present the full set of functions a user can use. The initial set of functions not seen are the aggregates (maybe there are others), sum, count, avg, etc., that we support.
--
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
10 years, 2 months
[JBoss JIRA] (TEIIDDES-2092) Consolidate Data Source connection management into a single view
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2092?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2092:
-----------------------------------
Fix Version/s: 8.6
(was: 8.5)
Priority: Major (was: Blocker)
Pretty involved feature that needs dedicated design time. Pushing to 8.6
> Consolidate Data Source connection management into a single view
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2092
> URL: https://issues.jboss.org/browse/TEIIDDES-2092
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Datatools Integration, Teiid Integration, Views
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.6
>
> Attachments: data-sources-view-draft.png
>
>
> Teiid Designer, and JBoss Tools in general, suffers from the lack of a centralized view of workspace datasource/connection information.
> This feature may include:
> * Data Sources view
> ** Tree containing datasource category/type folders (i.e. JDBC, WS, File, Spreadsheet etc.... ) and instances of Datasource Definitions
> ** Property table to show/edit properties for selected Datasource Definitions
> ** Toolbar to allow creating DDs, creating/deploying datasources from selected DDs
> ** Actions would include: Create Data Source, Import > JDBC or through Teiid Connection
--
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
10 years, 2 months
[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1822:
-----------------------------------
Fix Version/s: 8.6
(was: 8.5)
Server log still shows ACTIVE and INACTIVE states. Doesn't make sense for Designer to use different terminology at this time. Pushing to 8.6
> Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1822
> URL: https://issues.jboss.org/browse/TEIIDDES-1822
> Project: Teiid Designer
> Issue Type: Task
> Components: VDB & Execution
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 8.6
>
>
> 1) Set-up simple JDBC source/model/vdb and test/execute VDB
> 2) Delete the Data Source in the Server view
> 3) Try and execute the VDB again and get exception logged in console
> Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check.
--
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
10 years, 2 months
[JBoss JIRA] (TEIIDDES-2118) Invalid message when jdbc password is set to other than default
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2118?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-2118:
-------------------------------------------
Fixed in master. Needs porting over to 8.3.x branch
> Invalid message when jdbc password is set to other than default
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2118
> URL: https://issues.jboss.org/browse/TEIIDDES-2118
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.3.1, 8.5
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.3.2, 8.5
>
>
> The erroneous message of "Cannot find Driver" is displayed when a teiid jdbc connection is attempted yet the driver password does not match that of the user on the server. This is due to inaccurate handling of exceptions thrown when driver.connect is called.
> Consider how to handle a jump-in to allow the user to change the password if incorrect.
--
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
10 years, 2 months
[JBoss JIRA] (TEIIDDES-2093) Populate the "import" properties defined for translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2093?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2093:
--------------------------------------
Assignee: Barry LaFond
> Populate the "import" properties defined for translator
> -------------------------------------------------------
>
> Key: TEIIDDES-2093
> URL: https://issues.jboss.org/browse/TEIIDDES-2093
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.5
>
>
> With TEIID-2904, Teiid 8.7 will contain a facility to retrieve the import properties for a translator that are used to customize the metadata import process through Admin API.
> Teiid Connection importer needs currently is designed to add ad-hoc import properties, and this can be enhanced to populate with this dynamic list, so that user does not have to search through documents for these import properties.
--
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
10 years, 2 months