[JBoss JIRA] (TEIIDDES-1656) Migrate and publish legacy E2E test scripts to community as how-to use-cases
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1656:
--------------------------------------
Summary: Migrate and publish legacy E2E test scripts to community as how-to use-cases
Key: TEIIDDES-1656
URL: https://issues.jboss.org/browse/TEIIDDES-1656
Project: Teiid Designer
Issue Type: Task
Components: Documentation
Reporter: Barry LaFond
The legacy (MetaMatrix) E2E test scripts have been migrated in part to work with Teiid & Teiid Designer. With the change to Teiid 8.x server and new Teiid Designer features, it makes sense to fix and publish the appropriate test scripts as "How To" documents (WIKI).
This would include publishing the metadata used for these use-cases which use public Books, Employees, Products, Customers, Accounts, PartsSupplier data.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1655) Teiid importer needs to handle schema and catalog cases for generated model
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1655:
---------------------------------------
Summary: Teiid importer needs to handle schema and catalog cases for generated model
Key: TEIIDDES-1655
URL: https://issues.jboss.org/browse/TEIIDDES-1655
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.1
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.2
When importing via the Teiid Importer, an example of Teiid DDL for tables:
CREATE FOREIGN TABLE "accounts.ACCOUNT" (
COL1 long NOT NULL DEFAULT '0' OPTIONS (..., NAMEINSOURCE '`ACCOUNT_ID`', ...),
) OPTIONS (..., NAMEINSOURCE '`accounts`.`ACCOUNT`', ...);
Since some dbs support catalogs, the 'dotted' names can be multiple levels deep. We need to use a combination of NameInSource and potentially filtering on the DDL retrieval to determine how the model entities are to be created.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1654) DDL Importer needs to better handle constraint naming in generated model
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1654:
---------------------------------------
Summary: DDL Importer needs to better handle constraint naming in generated model
Key: TEIIDDES-1654
URL: https://issues.jboss.org/browse/TEIIDDES-1654
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.1
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.2
When importing DDL, the generated model can have errors when multiple constraints are present. For example the following DDL:
CREATE FOREIGN TABLE G1( e1 integer, e2 varchar, e3 date, PRIMARY KEY (e1, e2), INDEX(e2, e3), ACCESSPATTERN(e1), UNIQUE(e1), ACCESSPATTERN(e2, e3))
includes two access patterns which end up being named the same. The importer should auto increment the names to avoid name conflicts.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1336) Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1336?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1336:
--------------------------------------
Fix Version/s: 8.2
(was: 8.1)
> Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1336
> URL: https://issues.jboss.org/browse/TEIIDDES-1336
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Datatools Integration, Web Services Support
> Affects Versions: 7.7
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Both teiid and designer provide the authenticated WSDL securityType choices of None, BasicHTTP and WS-Security. Consideration in the Designer connection profile and imported wizards has been focused on supporting the 'None' and 'BasicHTTP' options. The WS-Security option should also be evaluated to determine the work required to fully support it or else decide that it is currently unnecessary and thus disable/remove it. This impacts both the SOAP WSDL related importers and REST importers.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1336) Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1336?page=com.atlassian.jira.plu... ]
Paul Richardson updated TEIIDDES-1336:
--------------------------------------
Priority: Major (was: Minor)
> Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1336
> URL: https://issues.jboss.org/browse/TEIIDDES-1336
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Datatools Integration, Web Services Support
> Affects Versions: 7.7
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> Both teiid and designer provide the authenticated WSDL securityType choices of None, BasicHTTP and WS-Security. Consideration in the Designer connection profile and imported wizards has been focused on supporting the 'None' and 'BasicHTTP' options. The WS-Security option should also be evaluated to determine the work required to fully support it or else decide that it is currently unnecessary and thus disable/remove it. This impacts both the SOAP WSDL related importers and REST importers.
--
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, 12 months
[JBoss JIRA] (TEIIDDES-1652) Preview VDB for Teiid Source imported table contains loopback translator type
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1652?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1652:
----------------------------------------
I was able to delete that model's Preview VDB and re-execute the preview. This forced the creation of a NEW preview VDB and it worked just fine.
So when I "Set Connection Profile" the PreviewManager wasn't correctly notified that the model had changed and that the Preview VDB needed to get re-created.
> Preview VDB for Teiid Source imported table contains loopback translator type
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-1652
> URL: https://issues.jboss.org/browse/TEIIDDES-1652
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 8.1
>
>
> * Installed a new kit with Teiid Source DDL importer option
> * Imported from SQL Server Parts schema to create PartsSupplier model
> * Tried to preview right away and got "Set Connection Profile" warning
> * Set connection profile
> * Previewed and it returned Loopback "ABCDEFJHI" data
> * Checked deployed Preview VDB vdb.xml and translator-name == "loopback"
--
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
13 years
[JBoss JIRA] (TEIIDDES-1652) Set Connection Profile action not correctly broadcasting resource change, so preview vdb isn't re-created
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1652?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1652:
-----------------------------------
Summary: Set Connection Profile action not correctly broadcasting resource change, so preview vdb isn't re-created (was: Preview VDB for Teiid Source imported table contains loopback translator type)
> Set Connection Profile action not correctly broadcasting resource change, so preview vdb isn't re-created
> ---------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1652
> URL: https://issues.jboss.org/browse/TEIIDDES-1652
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 8.1
>
>
> * Installed a new kit with Teiid Source DDL importer option
> * Imported from SQL Server Parts schema to create PartsSupplier model
> * Tried to preview right away and got "Set Connection Profile" warning
> * Set connection profile
> * Previewed and it returned Loopback "ABCDEFJHI" data
> * Checked deployed Preview VDB vdb.xml and translator-name == "loopback"
--
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
13 years