April 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-271) Object URi should be shown in Table Editor view - table column is empty

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-271?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-271. ----------------------------------- Resolution: Done Added check and call to insure the table editor's ModelObjectPropertySource descriptors map was initialized. The Properties view worked OK because the getPropertyDescriptors() method is called by Eclipse's PropertySource framework > Object URi should be shown in Table Editor view - table column is empty > ----------------------------------------------------------------------- > > Key: TEIIDDES-271 > URL: https://issues.jboss.org/browse/TEIIDDES-271 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Modeling > Affects Versions: 8.1 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.1 > > > If I declare an object URI for a model the object URIs of the model's children are not displayed in the Object URI column of the Table Editor view. Please make it happen. :-) -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-271) Object URi should be shown in Table Editor view - table column is empty

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-271?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-271: ---------------------------------- Issue Type: Bug (was: Task) Fix Version/s: 8.1 Affects Version/s: 8.1 Component/s: Editors Modeling > Object URi should be shown in Table Editor view - table column is empty > ----------------------------------------------------------------------- > > Key: TEIIDDES-271 > URL: https://issues.jboss.org/browse/TEIIDDES-271 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Modeling > Affects Versions: 8.1 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.1 > > > If I declare an object URI for a model the object URIs of the model's children are not displayed in the Object URI column of the Table Editor view. Please make it happen. :-) -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-275) Designer should collect cost analysis statistics at import time, by default, for any data source that supports it

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-275?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-275: --------------------------------------- Add an option in the JDBC Importer for users to check a "Include Cost Statistics" check-box. Tooltip should describe the impact (i.e. import could take much longer....) > Designer should collect cost analysis statistics at import time, by default, for any data source that supports it > ----------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-275 > URL: https://issues.jboss.org/browse/TEIIDDES-275 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Reporter: Michael Walker > Assignee: Mark Drilling > Fix For: 8.2 > > > Performance can be dramatically improved if cost statistics are gathered at design time, which turns on cost-based optimizations at run time. However, the majority of Genentech users fail to remember to import this information, because it is not part of the standard import process. > When importing metadata from any data source, we should present users with the option to collect cost analysis statistics during import, so long as the data source supports it (or if MMX can calculate it synthetically). > Of course, we could inform users that cost analysis may take add some time to the import process. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-275) Designer should collect cost analysis statistics at import time, by default, for any data source that supports it

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-275?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-275: ---------------------------------- Fix Version/s: 8.2 > Designer should collect cost analysis statistics at import time, by default, for any data source that supports it > ----------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-275 > URL: https://issues.jboss.org/browse/TEIIDDES-275 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Reporter: Michael Walker > Assignee: Mark Drilling > Fix For: 8.2 > > > Performance can be dramatically improved if cost statistics are gathered at design time, which turns on cost-based optimizations at run time. However, the majority of Genentech users fail to remember to import this information, because it is not part of the standard import process. > When importing metadata from any data source, we should present users with the option to collect cost analysis statistics during import, so long as the data source supports it (or if MMX can calculate it synthetically). > Of course, we could inform users that cost analysis may take add some time to the import process. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-180) Exception In JDBC Importer Because Of An Invalid Database User

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-180?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-180. --------------------------------- Resolution: Won't Fix Legacy 6.0 version. Won't fix > Exception In JDBC Importer Because Of An Invalid Database User > -------------------------------------------------------------- > > Key: TEIIDDES-180 > URL: https://issues.jboss.org/browse/TEIIDDES-180 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Environment: Ubuntu 8.04 > Reporter: Dan Florian > Fix For: Future > > > Running the "E2E Procedure Relational Mapping Test Script" I got the below exception after hitting "Next" in the JDBC import wizard's "Select Database Metadata" screen. The exception only appeared in the log and did not affect the test other than possibly making me manually select the correct database objects. > !MESSAGE Unexpected exception while calling com.microsoft.sqlserver.jdbc.SQLServerDatabaseMetaData.getTableTypes() and processing results on DatabaseAdventureWorks2000 > !STACK 0 > com.microsoft.sqlserver.jdbc.SQLServerException: Server user 'mmds' is not a valid user in database 'ACBIS'. > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) > at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:246) > at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:83) > at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:39) > at com.microsoft.sqlserver.jdbc.SQLServerConnection$1ConnectionCommand.doExecute(SQLServerConnection.java:1457) > at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(SQLServerConnection.java:1462) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.setCatalog(SQLServerConnection.java:1767) > at com.microsoft.sqlserver.jdbc.SQLServerDatabaseMetaData.switchCatalogs(SQLServerDatabaseMetaData.java:313) > at com.microsoft.sqlserver.jdbc.SQLServerDatabaseMetaData.getResultSetFromStoredProc(SQLServerDatabaseMetaData.java:264) > at com.microsoft.sqlserver.jdbc.SQLServerDatabaseMetaData.getResultSetWithProvidedColumnNames(SQLServerDatabaseMetaData.java:291) > at com.microsoft.sqlserver.jdbc.SQLServerDatabaseMetaData.getTables(SQLServerDatabaseMetaData.java:441) > at com.metamatrix.modeler.jdbc.metadata.impl.JdbcTableTypeImpl.computeChildren(JdbcTableTypeImpl.java:54) > at com.metamatrix.modeler.jdbc.metadata.impl.JdbcNodeImpl.getChildren(JdbcNodeImpl.java:185) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportObjectsPage.updateCounts(JdbcImportObjectsPage.java:595) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportObjectsPage.updateCounts(JdbcImportObjectsPage.java:595) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportObjectsPage.updateCounts(JdbcImportObjectsPage.java:595) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportObjectsPage.validatePage(JdbcImportObjectsPage.java:616) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportObjectsPage.refresh(JdbcImportObjectsPage.java:406) > at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportObjectsPage.setVisible(JdbcImportObjectsPage.java:307) -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1419) Docs - Need to clarify UDF usage in 7.7.2

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1419?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1419: ----------------------------------- Fix Version/s: 7.7.3 (was: 7.7.2) > Docs - Need to clarify UDF usage in 7.7.2 > ----------------------------------------- > > Key: TEIIDDES-1419 > URL: https://issues.jboss.org/browse/TEIIDDES-1419 > Project: Teiid Designer > Issue Type: Enhancement > Components: Documentation > Affects Versions: 7.7.1 > Reporter: Mark Drilling > Fix For: 7.7.3 > > > It is confusing in 7.7.1 how the user should create UDFs. > The process is the same in 7.7.1, but you get a deprecation warning when you create a function model. There is still work to be done with the MEDs for UDF creation - I think that is planned for 8.0. > In the meantime we should make it clear in the docs, that the process is the same re UDFs until 8.0 - even though you get a deprecation warning saying not to use the FunctionModel. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1457) ERROR: SYSADMIN.logMsg does not exist.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1457?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1457: ----------------------------------- Fix Version/s: 7.7.3 (was: 7.7.2) > ERROR: SYSADMIN.logMsg does not exist. > -------------------------------------- > > Key: TEIIDDES-1457 > URL: https://issues.jboss.org/browse/TEIIDDES-1457 > Project: Teiid Designer > Issue Type: Bug > Components: Testing > Affects Versions: 7.7 > Environment: Windows 7 64 bits > Reporter: Mónica L.A. > Fix For: 7.7.3 > > > I've just put different calls to SYSADMIN.logMsg to trace a procedure and when I save, the transformation editor show the message: ERROR: SYSADMIN.logMsg does not exist -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1633) XML Namespaces are not imported for Child Element

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1633?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1633: -------------------------------- Fix Version/s: 8.2 > XML Namespaces are not imported for Child Element > ------------------------------------------------- > > Key: TEIIDDES-1633 > URL: https://issues.jboss.org/browse/TEIIDDES-1633 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.6 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 8.2 > > > XML Namespaces are not imported for Child Elements while creating XML Document model. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1348) Investigate Adding Additional VDB Properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1348?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1348: ----------------------------------- Fix Version/s: 8.2 (was: Future) > Investigate Adding Additional VDB Properties > -------------------------------------------- > > Key: TEIIDDES-1348 > URL: https://issues.jboss.org/browse/TEIIDDES-1348 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 7.7 > Reporter: Ted Jones > Priority: Minor > Fix For: 8.2 > > > We currently allow the user to set the query timeout on the VDB. We had a request from the field to see if there were other properties we could set at that level and add to the tab. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1442) The export and then import of the project set causes models to be invalid

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1442?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1442. ------------------------------------ Resolution: Cannot Reproduce Bug Tested with 8.1 Alpha2. no issues > The export and then import of the project set causes models to be invalid > ------------------------------------------------------------------------- > > Key: TEIIDDES-1442 > URL: https://issues.jboss.org/browse/TEIIDDES-1442 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Barry LaFond > Attachments: Lab_0007.zip > > > See the attached project set. > Can reproduce by doing the following: > 1 import the attached project set > 2 models are invalid (the contents of some models maybe missing) > 3 close and reopen project and the contents come back > 4 clean and rebuild > 5 export as a new project set > 6 restart at #1 > I have gone thru this cycle 5 times and yet to get a project cleanly imported. Which implies something is not being exported correctly. > Not to mention the contents of the models are missing sometimes after import and will reappear if the project is closed/opened. -- 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

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 April 2013