July 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2109) Create a Connections context menu group next to Modeling group

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2109?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2109: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Create a Connections context menu group next to Modeling group > -------------------------------------------------------------- > > Key: TEIIDDES-2109 > URL: https://issues.jboss.org/browse/TEIIDDES-2109 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Views > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.3 > > Attachments: connection-action-menu.png > > > For source models, the Modeling action now contains a number of connection or translator related actions that really don't have anything to do with modeling. > * Create a *Connection* menu group and place below *Modeling* group > * Move the following actions to the *Connection* group > ** Create Data Source > ** Edit Translator Overrides > ** Remove Connection Info > ** Set Connection Profile > ** Set Translator Name > ** View Connection Profile Info > * Maybe group these into Translator/Profile actions with separators -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2449) Add a uttility in Teiid Client plugin to construct a VDB Manifest (xml)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2449?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2449. ---------------------------------- Resolution: Rejected New import/export Dynamic VDBs will basically provide this functionality in Designer. > Add a uttility in Teiid Client plugin to construct a VDB Manifest (xml) > ----------------------------------------------------------------------- > > Key: TEIIDDES-2449 > URL: https://issues.jboss.org/browse/TEIIDDES-2449 > Project: Teiid Designer > Issue Type: Task > Components: Teiid Integration, VDB & Execution > Affects Versions: 9.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2 > > > In order to import full deployed VDBs on the server we'll need a mechanism to get Data Roles/Policies, Translator Overrides, etc. that are defined in a deployed VDB manifest. Unfortunately, Designer's ITeiidVdb is designed to be simple and the info is only available via Teiid's VDB interface, which isn't part of the Admin API. > Suggest creating a utility in the teiid.client plugin that can take a VDB and construct the basic Manifest, or -vdb.xml string down to the *<model/>* elements. > Then, by adding a *getManifest()* method to our ITeiidVdb interface, Designer can create a full DDL-based version of a deployed VDB using that method + the Teiid Server's getSchema() method. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1732: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Stream line steps to implement all the steps around materialization > -------------------------------------------------------------------- > > Key: TEIIDDES-1732 > URL: https://issues.jboss.org/browse/TEIIDDES-1732 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.3 > > > Would like to stream line the steps to putting materialization to work. Example: > - Right mouse click on view, select materialization > - present wizard to walk thru the following options: > - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created) > - put name of mat table into the selected table/view to be materialized > - [optional] export DDL (file system or clipboard) > - [optional] create procedure that has the "select into" for refreshing > Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table. > Once thru this wizard, (I think) everything is in place to do materialization for the specified table. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2437) Enable specifying VDB Version when using VDB RE-USE feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2437?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2437: ----------------------------------- Description: When using the VDB re-use feature, need to be able to set the VDB version for the import VDB to be dependent upon. <import-vdb name="Products" version="3" import-data-policies="true"/> was:When using the VDB re-use feature, need to be able to set the VDB version for the import VDB to be dependent upon. > Enable specifying VDB Version when using VDB RE-USE feature > ----------------------------------------------------------- > > Key: TEIIDDES-2437 > URL: https://issues.jboss.org/browse/TEIIDDES-2437 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.2 > > > When using the VDB re-use feature, need to be able to set the VDB version for the import VDB to be dependent upon. > <import-vdb name="Products" version="3" import-data-policies="true"/> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ] Juraj Duráni edited comment on TEIIDDES-2458 at 7/7/15 2:18 AM: ---------------------------------------------------------------- I think that this could be a driver issue. We can try to get the newest version of jconn. Or we could switch to jtds. However I am not sure if PM would ack this. was (Author: jdurani): I think that this could be a driver issue. We can try to get the newest version of jconn. > Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database) > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2458 > URL: https://issues.jboss.org/browse/TEIIDDES-2458 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: JBDS: 8.0.2GA > TD: 9.0.1.Final > OS: Fedora 20 > java: oracle 1.7 > JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502) > Sybase DB: ASE 15.0.3/EBF > Reporter: Juraj Duráni > Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png > > > I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ] Juraj Duráni commented on TEIIDDES-2458: ---------------------------------------- I think that this could be a driver issue. We can try to get the newest version of jconn. > Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database) > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2458 > URL: https://issues.jboss.org/browse/TEIIDDES-2458 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: JBDS: 8.0.2GA > TD: 9.0.1.Final > OS: Fedora 20 > java: oracle 1.7 > JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502) > Sybase DB: ASE 15.0.3/EBF > Reporter: Juraj Duráni > Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png > > > I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2571) Add HTTP Digest Authentication Support for Web Services as a Source

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-2571: ----------------------------------- Summary: Add HTTP Digest Authentication Support for Web Services as a Source Key: TEIIDDES-2571 URL: https://issues.jboss.org/browse/TEIIDDES-2571 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export, Web Services Support Affects Versions: 9.0.3, 9.3 Reporter: Ted Jones Assignee: Ted Jones Need to support importing web services that use HTTP Basic authentication -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2497) Incorrect "Name in Source" when importing from JDBC Database using Informix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2497?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2497: ----------------------------------- Attachment: org.teiid.designer.jdbc.relational.patch org.teiid.designer.jdbc.patch > Incorrect "Name in Source" when importing from JDBC Database using Informix > --------------------------------------------------------------------------- > > Key: TEIIDDES-2497 > URL: https://issues.jboss.org/browse/TEIIDDES-2497 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Bruno Machado > Assignee: Barry LaFond > Labels: designer, informix, metadata, teiid > Fix For: 9.2, 9.0.3 > > Attachments: org.teiid.designer.jdbc.patch, org.teiid.designer.jdbc.relational.patch > > > When importing from JDBC Database using a Informix connection, an incorrect "Name in source" metadata is set as "catalog":"schema":"table-name" instead of "catalog":"schema"."table-name", the delimiter between schema and table-name is set to ':' but Informix uses '.'. > The ':' character must be replaced by a '.' between schema and table name when importing informix tables using Import From JDBC Database. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2497) Incorrect "Name in Source" when importing from JDBC Database using Informix

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2497?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2497: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1240343 > Incorrect "Name in Source" when importing from JDBC Database using Informix > --------------------------------------------------------------------------- > > Key: TEIIDDES-2497 > URL: https://issues.jboss.org/browse/TEIIDDES-2497 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Bruno Machado > Assignee: Barry LaFond > Labels: designer, informix, metadata, teiid > Fix For: 9.2, 9.0.3 > > > When importing from JDBC Database using a Informix connection, an incorrect "Name in source" metadata is set as "catalog":"schema":"table-name" instead of "catalog":"schema"."table-name", the delimiter between schema and table-name is set to ':' but Informix uses '.'. > The ':' character must be replaced by a '.' between schema and table name when importing informix tables using Import From JDBC Database. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2497) Incorrect "Name in Source" when importing from JDBC Database using Informix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2497?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2497: ----------------------------------- Fix Version/s: 9.2 9.0.3 > Incorrect "Name in Source" when importing from JDBC Database using Informix > --------------------------------------------------------------------------- > > Key: TEIIDDES-2497 > URL: https://issues.jboss.org/browse/TEIIDDES-2497 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0 > Reporter: Bruno Machado > Assignee: Barry LaFond > Labels: designer, informix, metadata, teiid > Fix For: 9.2, 9.0.3 > > > When importing from JDBC Database using a Informix connection, an incorrect "Name in source" metadata is set as "catalog":"schema":"table-name" instead of "catalog":"schema"."table-name", the delimiter between schema and table-name is set to ':' but Informix uses '.'. > The ':' character must be replaced by a '.' between schema and table name when importing informix tables using Import From JDBC Database. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2015