April 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-931) Change the default to qualify name in source

by Steven Hawkins (JIRA)

Change the default to qualify name in source -------------------------------------------- Key: TEIIDDES-931 URL: https://issues.jboss.org/browse/TEIIDDES-931 Project: Teiid Designer Issue Type: Quality Risk Reporter: Steven Hawkins Fully qualified name in source entries are a safe default. Just using table names can lead to conflicts. Also using just table names prevents the costing logic from working. It would almost be best if we didn't even offer the ability to use unqualified names. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-930) Add Support for Mondrian (OLAP)

by Ramesh Reddy (JIRA)

Add Support for Mondrian (OLAP) ------------------------------- Key: TEIIDDES-930 URL: https://issues.jboss.org/browse/TEIIDDES-930 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: Ramesh Reddy Teiid 7.4 version adds a new OLAP Translator. This translator mimics more like File translator. Designer needs to add support for this translator. In order to use this translator supported procedure, Designer also need to support "arraytable", I think once the Designer libraries are upgraded to 7.4 this will be generally available. Until this JIRA is user can always hand model the procedure for OLAP source, which in the from ResultSet invokeMDX(String mdxQuery) The Resultset above should have a single column called "tuple" with data type "Object". During the runtime, this Object is really Object[] that can be used as below select t.* from (call invokeMDX('query')) x, arraytable(x.tuple COLUMNS col1 string, col2 integer) t; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-929) SUID labels for source table in transformation diagram do not reflect SUID in transformation editor

by Barry LaFond (JIRA)

SUID labels for source table in transformation diagram do not reflect SUID in transformation editor ---------------------------------------------------------------------------------------------------- Key: TEIIDDES-929 URL: https://issues.jboss.org/browse/TEIIDDES-929 Project: Teiid Designer Issue Type: Bug Components: Diagrams, Editors, Transformations Affects Versions: 7.3, 7.4 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Minor Fix For: 7.4 The Transformation Editor changes to support new "default" Insert, Update and Delete resulted in the SUID letter labels not displaying proper state above the source table in transformation diagram. Traced it to logic in TransformationHelper that was looking at "allowsUpdate(t-root)" and whether the UUID Sql string was NOT NULL. The UUID Sql string is no longer used. Need to change logic to look for: 1) allowsUpdate() 2) either (isUpdateSqlDefault() || update user SQL != null ) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-928) Remove Test Feature From Site

by Dan Florian (JIRA)

Remove Test Feature From Site ----------------------------- Key: TEIIDDES-928 URL: https://issues.jboss.org/browse/TEIIDDES-928 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 7.3 Reporter: Dan Florian Assignee: Dan Florian Priority: Critical Fix For: 7.4 Need to remove the test feature from the site.xml. I had put that in temporarily while working on getting the tests running and forgot to take it out. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-925) Transformation Reconciler action is disabled too much. Need to enable for resolvable query AND keep enabled when SQL doesn't change.

by Barry LaFond (JIRA)

Transformation Reconciler action is disabled too much. Need to enable for resolvable query AND keep enabled when SQL doesn't change. ------------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-925 URL: https://issues.jboss.org/browse/TEIIDDES-925 Project: Teiid Designer Issue Type: Bug Components: Editors, Transformations Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.4 Transformation Reconciler action needs to stay enabled more. 1) Validate SQL that's fully resolvable and action is DISABLED 2) Edit/Dirty a model outside the T-Editor with valid SQL and action ENABLED will end up DISABLING action. Need to be more inclusive on enablement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-922) Create new translator override dialog in VDB editor has some message layout problems

by Barry LaFond (JIRA)

Create new translator override dialog in VDB editor has some message layout problems ------------------------------------------------------------------------------------ Key: TEIIDDES-922 URL: https://issues.jboss.org/browse/TEIIDDES-922 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.4 1) With NO Teiid Server available, open VDB for editing, click on Translator Overrides tab 2) Click the "+" action to add a new translator override 3) Initial message has funky line-break 4) Enter some "name" value and get error "A translator override must have a type" 5) Start entering a "type" value and the message returns but with a different line-break and some text is hidden. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-768) Criteria Builder may insert crieria inside object names if user not careful

by Paul Nittel (JIRA)

Criteria Builder may insert crieria inside object names if user not careful --------------------------------------------------------------------------- Key: TEIIDDES-768 URL: https://issues.jboss.org/browse/TEIIDDES-768 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.1.1 Environment: JBDS 4.0 Beta2 Reporter: Paul Nittel I start with: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM PartsSource.PARTS; END At this point the Criteria Builder (and Expression Builder) button is disabled. So I click in the SELECT clause to enable the button. Let's say I click between the P and the A of .PARTS. The button enables, I craft my WHERE clause, click OK and wind up with: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM PartsSource.PA WHERE PartsSource.PARTS.PART_COLOR = PartsView.getPartsByColor.colorInRTS; END Regardless of where in the SELECT I click, the WHERE clause should be inserted in a syntactically correct location. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-924) Error creating virtual model with multi_byte characters - Lexical error: Lexical error at line 1, column 30. Encountered: "\u00e5" (229), after : ""

by Warren Gibson (JIRA)

Error creating virtual model with multi_byte characters - Lexical error: Lexical error at line 1, column 30. Encountered: "\u00e5" (229), after : "" ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-924 URL: https://issues.jboss.org/browse/TEIIDDES-924 Project: Teiid Designer Issue Type: Bug Components: Transformations Reporter: Warren Gibson Attachments: ScreenShot001.bmp The objective of this test was to test multi_byte handling from a Postgres DB through the modeling process and ultimately querying a VDB. This includes multi byte (Chinese characters) in the table name, column names, and the data base data. I used a Postgres DB for the test. I was able to connect and successfully query the DB with a direct connection using pgAdmin III, SqlWorkbench, and Squirrel receiving the correct Chinese characters back. However, I have encountered a problem when attempting to model using the DB. I created a project in Designer and imported the DB table. The imported model appear to be correct in Designer (at least the Table and columns show up with Chinese characters and no errors are visible. See ScreenShot001.bmp However when I create a virtual view model by transforming it from the imported model I get the following error: Lexical error: Lexical error at line 1, column 30. Encountered: "\u00e5" (229), after : "" multi_byte_virtual.xmi /multi_byte åƒ_å__ I can provide the Postgres DB url if you need it. The project is attached: multi_byte.zip -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-914) Unable to deploy war generated through Jbossws-CXF using teiid designer 7.1.0 in Jboss 5.1.0 AS

by Hilal Mushtaque (JIRA)

Unable to deploy war generated through Jbossws-CXF using teiid designer 7.1.0 in Jboss 5.1.0 AS ----------------------------------------------------------------------------------------------- Key: TEIIDDES-914 URL: https://issues.jboss.org/browse/TEIIDDES-914 Project: Teiid Designer Issue Type: Feature Request Components: Web Services Support Reporter: Hilal Mushtaque Hi, I am unable to deploy the Web-Service war generated through jbossws-CXF using teiid designer 7.1.0 in Jboss 5.1.0 AS, I am getting below given error on the JBOSS Console DEPLOYMENTS IN ERROR: Deployment "vfszip:/E:/jboss-5.1.0.GA/jboss-5.1.0.GA/server/default/deploy/webService.war/" is in error due to the following reason(s): java.net.ConnectException: Connection refused: connect at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) :faultCode=PARSER_ERROR: Problem parsing 'http://www.metamatrix.com/metamodels/SimpleDatatypes-instance'.: java.net.ConnectException: Connection refused: connect Please suggest ASAP. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
20
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-920) IllegalArgumentException in Export DDL Wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-920?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-920. ----------------------------------- Resolution: Done Added name (*.xmi) and class (IFile) values to extension contribution. Added a selection check during initialization to prevent exception in the event that a non-Relational XMI file is selected. > IllegalArgumentException in Export DDL Wizard > --------------------------------------------- > > Key: TEIIDDES-920 > URL: https://issues.jboss.org/browse/TEIIDDES-920 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.2, 7.3 > Environment: JBDS 4.0.GA, linux 32bit > Reporter: Pavol Srna > Assignee: Barry LaFond > Fix For: 7.4 > > > Exception Stack Trace: > java.lang.IllegalArgumentException: Expected argument to be non-null but got null > at com.metamatrix.core.util.CoreArgCheck.isNotNull(CoreArgCheck.java:139) > at com.metamatrix.core.util.CoreArgCheck.isNotNull(CoreArgCheck.java:125) > at com.metamatrix.modeler.core.workspace.ModelWorkspaceView.findObject(ModelWorkspaceView.java:135) > at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard.createPageControl(ExportDdlWizard.java:483) > at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard$2.createControl(ExportDdlWizard.java:225) > at com.metamatrix.ui.internal.wizard.AbstractWizard.createPageControls(AbstractWizard.java:152) > at com.metamatrix.ui.internal.wizard.AbstractWizard.createPageControls(AbstractWizard.java:137) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:734) > at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1162) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1221) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1218) > at org.eclipse.jface.wizard.WizardDialog$6.run(WizardDialog.java:1207) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1205) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:894) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:426) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) > at org.eclipse.jface.window.Window.open(Window.java:801) > at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:98) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) > at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > 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:1258) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > 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:369) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) > at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2011