[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1575.
-------------------------------------
Resolution: Done
Closing - the importer has been incorporated. I have targeted related dependent JIRAs to 8.2 for further testing.
> Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1575
> URL: https://issues.jboss.org/browse/TEIIDDES-1575
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 8.1
>
> Attachments: ImporterPage1.png, ImporterPage2.png, WizardPage1.bmml, WizardPage1.bmml, WizardPage1.png, WizardPage2.bmml, WizardPage2.png, WizardPage3.bmml, WizardPage3.png
>
>
> Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server.
> We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer.
> Potential DBs include:
> * Hive - TEIIDDES-1193
> * Mondrian - TEIIDDES-930
> * Intersystems Cache - TEIIDDES-904
> * Ingres - TEIIDDES-883
> * LDAP - TEIIDDES-305
> * Greenplum - TEIIDDES-1557
--
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
12 years, 11 months
[JBoss JIRA] (TEIIDDES-930) Add Support for Mondrian (OLAP)
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-930?page=com.atlassian.jira.plug... ]
Mark Drilling updated TEIIDDES-930:
-----------------------------------
Assignee: Mark Drilling
Fix Version/s: 8.2
Affects Version/s: 8.0
> Add Support for Mondrian (OLAP)
> -------------------------------
>
> Key: TEIIDDES-930
> URL: https://issues.jboss.org/browse/TEIIDDES-930
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 8.0
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.2
>
>
> Teiid 7.4 version adds a new OLAP Translator. This translator mimics more like File translator. Designer needs to add support for this translator. In order to use this translator supported procedure, Designer also need to support "arraytable", I think once the Designer libraries are upgraded to 7.4 this will be generally available. Until this JIRA is user can always hand model the procedure for OLAP source, which in the from
> ResultSet invokeMDX(String mdxQuery)
> The Resultset above should have a single column called "tuple" with data type "Object". During the runtime, this Object is really Object[] that can be used as below
> select t.* from (call invokeMDX('query')) x, arraytable(x.tuple COLUMNS col1 string, col2 integer) t;
--
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
12 years, 11 months
[JBoss JIRA] (TEIIDDES-1683) Incorrect metadata for teiid runtime client feature
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-1683:
-----------------------------------------
Summary: Incorrect metadata for teiid runtime client feature
Key: TEIIDDES-1683
URL: https://issues.jboss.org/browse/TEIIDDES-1683
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 8.1
Reporter: Paul Richardson
Assignee: Paul Richardson
Fix For: 8.1
When installing the beta, the licence and provider name for the teiid runtime client feature are incorrect. Some properties are not being set or included leading to the identifiers 'licence' and 'provideName' being used instead.
--
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
12 years, 11 months
[JBoss JIRA] (TEIIDDES-1682) Exception Creating UDF In A View Model Trying To Set "relational:null-on-null" Property
by Dan Florian (JIRA)
Dan Florian created TEIIDDES-1682:
-------------------------------------
Summary: Exception Creating UDF In A View Model Trying To Set "relational:null-on-null" Property
Key: TEIIDDES-1682
URL: https://issues.jboss.org/browse/TEIIDDES-1682
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.0
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 8.1
Creating a UDF in a view model I get this:
!MESSAGE Error setting extension properties on Abc
!STACK 0
java.lang.Exception: The property definition "relational:null-on-null" could not be found.
at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.setPropertyValue(EmfModelObjectExtensionAssistant.java:485)
at org.teiid.designer.metamodels.relational.extension.RelationalModelExtensionAssistant.setPropertyValue(RelationalModelExtensionAssistant.java:241)
at org.teiid.designer.relational.model.RelationalModelFactory.applyProcedureExtensionProperties(RelationalModelFactory.java:789)
at org.teiid.designer.transformation.model.RelationalViewModelFactory.buildObject(RelationalViewModelFactory.java:160)
at org.teiid.designer.relational.model.RelationalModelFactory.buildFullModel(RelationalModelFactory.java:200)
at org.teiid.designer.transformation.model.RelationalViewModelFactory.build(RelationalViewModelFactory.java:110)
at org.teiid.designer.transformation.ui.actions.CreateViewProcedureAction.createViewProcedureInTxn(CreateViewProcedureAction.java:207)
at org.teiid.designer.transformation.ui.actions.CreateViewProcedureAction.run(CreateViewProcedureAction.java:182)
--
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
12 years, 11 months
[JBoss JIRA] (TEIIDDES-1577) Changing connection URL for JDBC driver has no effect
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1577?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1577.
-------------------------------------
Resolution: Done
Similar behavior was resolved under a different jira - https://issues.jboss.org/browse/TEIIDDES-1244 . One is that we no longer allow the connection properties to be changed on the property panel, which was confusing. The connection profile has to be reset on the model.
> Changing connection URL for JDBC driver has no effect
> -----------------------------------------------------
>
> Key: TEIIDDES-1577
> URL: https://issues.jboss.org/browse/TEIIDDES-1577
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Tom Johnston
> Assignee: Mark Drilling
> Fix For: 8.1
>
>
> Changing Connection URL under Properties Tab for Edit Driver Definitions does not have any impact when using the driver.
> I.E. When specifying a new connection profile the Connection URL (shaded, unchangeable here) does NOT reflect the aforementioned property.
> Use Case: I'm trying to create a new driver entry using Oracles OCI connectivity capability thus requiring a change in the connection url to (jdbc:oracle:oci:@<database_string> , for example)
--
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
12 years, 11 months