May 2013 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1707) Data Source Created Using Model Connection Info Does Not Work

by Dan Florian (JIRA)

Dan Florian created TEIIDDES-1707: ------------------------------------- Summary: Data Source Created Using Model Connection Info Does Not Work Key: TEIIDDES-1707 URL: https://issues.jboss.org/browse/TEIIDDES-1707 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 8.1 Reporter: Dan Florian I did a JDBC import that created a relational model. I right-clicked on the new model and Modeling > Create Data Source. On the Create Data Source dialog I entered a data source name and left every other value untouched. I had to enter a password after that dialog closed. Using the newly created data source in a Teiid Connection import fails because the URL of the data source does not have the database name. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1706) During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1706: -------------------------------------- Summary: During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties Key: TEIIDDES-1706 URL: https://issues.jboss.org/browse/TEIIDDES-1706 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.1 Reporter: Barry LaFond Fix For: 8.2 MergeProcessorImpl.doOrderContained() shows the following for source and result ModelAnnotationImpl. ProducerName and ProducerVersion are lost. sourceObject: org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@30298bbf (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: Teiid Designer, ProducerVersion: 8.2.0) resultObject: org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@d3b11c3 (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: null, ProducerVersion: null) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1660) DDL Importer should correct Primary Key referencing a nullable column

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1660?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1660. ------------------------------------ Assignee: Barry LaFond (was: Mark Drilling) Resolution: Done Done > DDL Importer should correct Primary Key referencing a nullable column > --------------------------------------------------------------------- > > Key: TEIIDDES-1660 > URL: https://issues.jboss.org/browse/TEIIDDES-1660 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.2 > > > If the DDL does not specify the nullability of a column, but the column is used as a primary key, the DDL Importer should go ahead and specify that the column is not nullable. If not this results in an error with the generated 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1259) USABILITY: When reconciling transformation and reserved word is encountered, can the error message indicate its a reserved word

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1259?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1259. ------------------------------------- Resolution: Done Teiid messages are shorter and more descriptive now - marking done. > USABILITY: When reconciling transformation and reserved word is encountered, can the error message indicate its a reserved word > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1259 > URL: https://issues.jboss.org/browse/TEIIDDES-1259 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Minor > Fix For: 8.2 > > > When the reconciler is validating the sql and a use of a reserved word is the cause of the invalidation, could the error message indicate as such? This may have already been done, but I didn't see a jira indicating it. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1705) Model imported from DDL is missing relational model extension MED

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1705: -------------------------------------- Summary: Model imported from DDL is missing relational model extension MED Key: TEIIDDES-1705 URL: https://issues.jboss.org/browse/TEIIDDES-1705 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 8.1 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 8.2 While working on TEIIDDES-1660 noticed that if I re-imported to same model an NPE showed up because the relational MED was not saved in the model. RelationalPlugin is responding to a New Model event and applying the MED, but later in the importer, the model contents is copied and it loses the MED. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1704) IllegalArgumentException getting CommandHelper.getProjectedSymbols(). getResultSetColumns() may be null

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1704?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1704. ------------------------------------ Resolution: Done added null check for getResultSetColumns() call > IllegalArgumentException getting CommandHelper.getProjectedSymbols(). getResultSetColumns() may be null > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1704 > URL: https://issues.jboss.org/browse/TEIIDDES-1704 > Project: Teiid Designer > Issue Type: Bug > Components: Validation > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.2 > > > If SQL contains CREATE VIRTUAL PROCEDURE BEGIN END, validation will result in an Illegal Arg exception because CreateProcedureCommand.getResultSetColumns() will return null and CommandHelper isn't checking for that. > Need to add the 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1699: ----------------------------------------- Assignee: Paul Richardson (was: Mark Drilling) > Issue with ServerView leads to Out of Memory condition > ------------------------------------------------------ > > Key: TEIIDDES-1699 > URL: https://issues.jboss.org/browse/TEIIDDES-1699 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Paul Richardson > Fix For: 8.2 > > > I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view. > In my situation, I have > 1) JBoss AS5.1 / Teiid 7.7 server > 2) JBoss AS7.1 / Teiid 8.3 servers > The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes. > I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet. > Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added? -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1699) Issue with ServerView leads to Out of Memory condition

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1699: ------------------------------------------- Since we would have the same AS and Teiid architectures, there would be nothing to distinguish them. Thus, we would need to fingerprint the server: * AS version * Teiid version * Location of the server on the filesystem The location might be most preferable since an upgrade to an existing server could result in version confusion. The downside I forsee with the location though is for remote servers but I think we can extract that too. Need to check ... > Issue with ServerView leads to Out of Memory condition > ------------------------------------------------------ > > Key: TEIIDDES-1699 > URL: https://issues.jboss.org/browse/TEIIDDES-1699 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > I'm running into out of memory with Designer in certain situations defining Teiid Servers in the Servers view. It is related to having different instances of the same server type in the view. > In my situation, I have > 1) JBoss AS5.1 / Teiid 7.7 server > 2) JBoss AS7.1 / Teiid 8.3 servers > The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out of memory and the designer crashes. > I suspect this has something to do with the registered servers not having unique identifier because the view looks like it is confusing the 8.3 servers. But I have not been able to pinpoint what is happening yet. > Also, I'm confused regarding the criteria for a server to be added to the registry. On Designer shutdown, I'm looking at the registry.xml and not all of the defined servers are included. Does a server need to be started in order for it to be added? -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1701) Deleting model open in dirty editor results in org.eclipse.swt.SWTException: Invalid thread access

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1701?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1701: ----------------------------------------- Assignee: Paul Richardson > Deleting model open in dirty editor results in org.eclipse.swt.SWTException: Invalid thread access > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1701 > URL: https://issues.jboss.org/browse/TEIIDDES-1701 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2 > > > 1) Open Model in Editor > 2) edit the model to make dirty (move object in diagram) > 3) Select Model in Explorer and click DELETE > 4) Get exception: > Root exception: > org.eclipse.swt.SWTException: Invalid thread access > at org.eclipse.swt.SWT.error(SWT.java:4361) > at org.eclipse.swt.SWT.error(SWT.java:4276) > at org.eclipse.swt.SWT.error(SWT.java:4247) > at org.eclipse.swt.widgets.Display.error(Display.java:1157) > at org.eclipse.swt.widgets.Display.checkDevice(Display.java:749) > at org.eclipse.swt.widgets.Display.getShells(Display.java:1939) > at org.eclipse.ui.internal.progress.ProgressManagerUtil.getModalShellExcluding(ProgressManagerUtil.java:286) > at org.eclipse.ui.internal.progress.ProgressManagerUtil.getDefaultParent(ProgressManagerUtil.java:340) > at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:950) > at org.eclipse.ui.internal.SaveableHelper.waitForBackgroundSaveJobs(SaveableHelper.java:463) > at org.eclipse.ui.internal.SaveablesList.promptForSaving(SaveablesList.java:466) > at org.eclipse.ui.internal.Workbench.saveAll(Workbench.java:3291) > at org.teiid.designer.ui.common.util.UiUtil.saveDirtyEditors(UiUtil.java:534) > at org.teiid.designer.ui.refactor.AbstractResourcesRefactoring.closeDirtyEditors(AbstractResourcesRefactoring.java:163) > at org.teiid.designer.ui.refactor.delete.DeleteResourcesRefactoring.checkInitialConditions(DeleteResourcesRefactoring.java:138) -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1703) Delete Model action default behavior is to delete all dependent models and probably not what users expects. Re-visit use-case

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1703?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-1703: ----------------------------------------- Assignee: Paul Richardson > Delete Model action default behavior is to delete all dependent models and probably not what users expects. Re-visit use-case > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1703 > URL: https://issues.jboss.org/browse/TEIIDDES-1703 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.2 > > > The new Refactor logic utilizes Eclipse's refactor/preview framework. Works GREAT. > Problem is, unlike deleting folders and projects, deleting a model will result in the default behavior of deleting any and all dependent models. For a WS model, this may include XSD files, XML Files and Source models. > Users can click "Preview>>" to view and deselect items for deletion, but this operation is probably NOT for the faint of heart. > Suggest maybe adding some verbage/warning on the FIRST page of the wizard so user knows that DEPENDENT files will be deleted. > Maybe add a "check-box" to change the default behavior to NOT delete dependent models. -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2013