August 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-576) NPE during Preview Data after turning Preview model off then back on

by Barry LaFond (JIRA)

NPE during Preview Data after turning Preview model off then back on -------------------------------------------------------------------- Key: TEIIDDES-576 URL: https://jira.jboss.org/browse/TEIIDDES-576 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.1 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.1 1) Fresh workspace (Preview model = TRUE) and live Teiid server 2) Import Relational Model 3) Select Table and Preview Data 4) Turn Preview mode = FALSE 5) Turn Previfew Mode = TRUE 6) Preview Data with same table 7) Get NPE Root exception: java.lang.NullPointerException at org.teiid.designer.runtime.preview.PreviewManager.getStatus(PreviewManager.java:633) at org.teiid.designer.runtime.preview.PreviewManager.needsToBeDeployed(PreviewManager.java:913) at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1050) at com.metamatrix.modeler.internal.dqp.ui.actions.PreviewTableDataContextAction$1.run(PreviewTableDataContextAction.java:327) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-527) The PreviewTableDataContextAction should block during the run method until the previewSetup() is complete before continuing with SQL set-up and execution.

by Barry LaFond (JIRA)

The PreviewTableDataContextAction should block during the run method until the previewSetup() is complete before continuing with SQL set-up and execution. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-527 URL: https://jira.jboss.org/browse/TEIIDDES-527 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.1 PreviewTableDataContextAction.run() method performs a Preview VBD setup. The results of this setup will submit/schedule one or more Jobs that need to be finished before the actual connection to Teiid VDB and SQL querying. Need to block until all jobs are done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-563) Preview VDB is being created as empty file. Will not deploy. Missing contents.

by Barry LaFond (JIRA)

Preview VDB is being created as empty file. Will not deploy. Missing contents. ------------------------------------------------------------------------------- Key: TEIIDDES-563 URL: https://jira.jboss.org/browse/TEIIDDES-563 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.1 Seems the changes to CreatePreviewVdbJob are now preventing new Preview Vdb's from being initially saved with the contents (i.e. vdb.xml manifest). Worked with Dan and we'll need to code for the case of the initial creation where we need to insure we call vdb.save(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-546) Designer's Preview Data feature needs an "on/off switch" to allow general modeling without intending to preview data

by Barry LaFond (JIRA)

Designer's Preview Data feature needs an "on/off switch" to allow general modeling without intending to preview data -------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-546 URL: https://jira.jboss.org/browse/TEIIDDES-546 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.1 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.1 After doing a bunch of development testing with no intent or focus on Preview Data feature, it's become apparent that there is performance overhead for the current Preview VDB framework trying to keep all models in sync with their Preview VDB's (i.e. hidden from user). We need an on/off switch preference which user can change. Maybe if it's "OFF", user will be queried when they launch Preview Data action, warn them and if they select OK, proceed to turn that preference back ON and proceed with preview setup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-452) Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function.

by Van Halbert (JIRA)

Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function. ------------------------------------------------------------------------------------------------- Key: TEIIDDES-452 URL: https://jira.jboss.org/browse/TEIIDDES-452 Project: Teiid Designer Issue Type: Feature Request Reporter: Van Halbert Fundamental rework of existing MetaMatrix materialized views functionality to make mat views first class objects in the system. The changes for this feature include: 1.Moving away from the automagic creation of materialized view source/physical model and ddl scripts upon VDB deployment 2.Making mat view source/physical models explictly modeled objects in Designer tooling. 3.Support external scripts to pull data from live sources and populate mat views. 4.Support virtual procedure logic to pull data from live sources and populate mat views. This will required DDL execution capabilities such that virtual procedures can perform the swap of staged data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-558) When creating WAR file, get: File not found, ...eclipse/configuration/org.eclipse.osgi/bundles/869/1/.cp//war_resources

by Paul Nittel (JIRA)

When creating WAR file, get: File not found, ...eclipse/configuration/org.eclipse.osgi/bundles/869/1/.cp//war_resources ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-558 URL: https://jira.jboss.org/browse/TEIIDDES-558 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid 7.1 M1 Designer Reporter: Paul Nittel Attachments: NoWarFile.zip I had previously modeled the Yahoo UDF VDB which contains a Web service. I right-clicked the VDB > Modeling > Create JBossWS CXF War. When I went to locate the file, I couldn't locate it or the directory in which it was to be created. Selecting alternate, existing directories also did not work as anticipated. Finally, I noticed I had been receiving errors in the Designer's message log: Error 2010-08-16 09:19:53.163 An error occurred while creating WAR file, check log for detail java.io.FileNotFoundException: The web lib directory, /home/pnittel/TDes71M1/eclipse/configuration/org.eclipse.osgi/bundles/869/1/.cp//war_resources, does not exist on the file system. at org.teiid.designer.dqp.webservice.war.DefaultWebArchiveBuilderImpl.getWebLibDirectoryPath(DefaultWebArchiveBuilderImpl.java:524) at org.teiid.designer.dqp.webservice.war.DefaultWebArchiveBuilderImpl.getWebFiles(DefaultWebArchiveBuilderImpl.java:372) at org.teiid.designer.dqp.webservice.war.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:222) at org.teiid.designer.dqp.webservice.war.ui.wizards.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:184) at org.teiid.designer.dqp.webservice.war.ui.wizards.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.teiid.designer.dqp.webservice.war.ui.wizards.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.teiid.designer.runtime.ui.GenerateWarAction.run(GenerateWarAction.java:93) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) I'll attach a Model Project Set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-259) UDF model file needs to bundled with VDB

by Ramesh Reddy (JIRA)

UDF model file needs to bundled with VDB ---------------------------------------- Key: TEIIDDES-259 URL: https://jira.jboss.org/jira/browse/TEIIDDES-259 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Reporter: Ramesh Reddy Currently (<6.3) the UDF model (FunctionDefinitions.xmi) file is supplied to Teiid Runtime separately. Starting with 7.0 release this file will be only accepted if it is bundled inside the VDB artifact. Designer needs to be modified to bundle this file inside the VDB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-531) Default Teiid Instance Is Not Restored At Startup

by Dan Florian (JIRA)

Default Teiid Instance Is Not Restored At Startup ------------------------------------------------- Key: TEIIDDES-531 URL: https://jira.jboss.org/browse/TEIIDDES-531 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.0 Reporter: Dan Florian Fix For: 7.2 The Teiid View is restored at startup with all Teiid instances that were registeeiired in the Teiid View during the last session. However, which of these Teiid instances that was functioning as the default or preview instance is not restored. The default/preview Teiid instance from the last session should be restored at startup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-571) Teiid view needs to indicate when a server is NOT connected.

by Barry LaFond (JIRA)

Teiid view needs to indicate when a server is NOT connected. ------------------------------------------------------------ Key: TEIIDDES-571 URL: https://jira.jboss.org/browse/TEIIDDES-571 Project: Teiid Designer Issue Type: Task Components: Views Affects Versions: 7.0 Reporter: Barry LaFond Priority: Critical Fix For: 7.1 Teiid view does not show status of a Teiid server connection and it should. Actions also need to know the state of a Teiid server connection else they might error-out. So. Let's add a Server.isConnected() method rather than rely on Server.ping() method which returns a Status. The Teiid view could check on every refresh() if a server is connected or not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-490) Validation of transformation SQL with sub-select and alias incorrectly adds model name to alias.column name

by Paul Nittel (JIRA)

Validation of transformation SQL with sub-select and alias incorrectly adds model name to alias.column name ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-490 URL: https://jira.jboss.org/browse/TEIIDDES-490 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Designer 6/28 Reporter: Paul Nittel This is from teh TPCR metadata text import test. A series of transformations is built for query testing. When I ran it, several transformations were affected similarly. The Hawkman looked at it and believes the issue lies within the Designer. Here's a simplified version of the SQL: SELECT supp_nation, cust_nation FROM (SELECT n1.N_NAME AS supp_nation, n2.N_NAME AS cust_nation FROM TPCR.SUPPLIER, TPCR.NATION AS n1, TPCR.NATION AS n2 WHERE (S_NATIONKEY = n1.N_NATIONKEY) ) AS shipping Upon validation, it changes to: SELECT SHIPPING.supp_nation, SHIPPING.cust_nation FROM (SELECT n1.TPCR.NATION.N_NAME AS supp_nation, n2.TPCR.NATION.N_NAME AS cust_nation FROM TPCR.SUPPLIER, TPCR.NATION AS n1, TPCR.NATION AS n2 WHERE TPCR.SUPPLIER.S_NATIONKEY = n1.TPCR.NATION.N_NATIONKEY) AS shipping The error is: The query is parsable but not resolvable. Resolver Error: Symbol n1.TPCR.NATION.N_NATIONKEY is specified with an unknown group context The element in question should be referred to as: n1.N_NATIONKEY. (I'll attach the model project set.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2010