November 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-711) SyncFailedException: Deployment content already exists

by Pavol Srna (JIRA)

SyncFailedException: Deployment content already exists ------------------------------------------------------ Key: TEIIDDES-711 URL: https://jira.jboss.org/browse/TEIIDDES-711 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Environment: JBDS 4.0.0.Beta1, SOA-5.1.0.ER3, Teiid 7.1, linux 32bit Reporter: Pavol Srna When trying to re-deploy VDB to the server, following error occurs: Message: ----------------- Problem deploying VDB: MyFirstVDB.vdb to server: mm://localhost:31443 Exception stack trace: -------------------------------- [AdminComponentException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 1 [AdminComponentException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 2 [AdminProcessingException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 3 [RuntimeException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 4 [SyncFailedException]Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72) at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler.invoke(SocketServerInstanceImpl.java:365) at org.teiid.net.socket.SocketServerConnection$1.invoke(SocketServerConnection.java:216) at $Proxy16.deployVDB(Unknown Source) 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.teiid.adminapi.AdminFactory$AdminProxy.invoke(AdminFactory.java:80) at $Proxy16.deployVDB(Unknown Source) at org.teiid.designer.runtime.ExecutionAdmin.deployVdb(ExecutionAdmin.java:121) at org.teiid.designer.runtime.ui.DeployVdbAction$1.run(DeployVdbAction.java:115) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.teiid.designer.runtime.ui.DeployVdbAction.deployVdb(DeployVdbAction.java:108) at org.teiid.designer.runtime.ui.DeployVdbAction.run(DeployVdbAction.java:82) 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: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) Caused by: [AdminComponentException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 1 [AdminProcessingException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 2 [RuntimeException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 3 [SyncFailedException]Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72) at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:252) at $Proxy359.deployVDB(Unknown Source) 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.teiid.transport.ServerWorkItem.run(ServerWorkItem.java:81) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.transport.SocketClientInstance.processMessagePacket(SocketClientInstance.java:161) at org.teiid.transport.SocketClientInstance.receivedMessage(SocketClientInstance.java:150) at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:210) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:317) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:214) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:340) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:272) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:192) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: [AdminProcessingException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 1 [RuntimeException]java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb 2 [SyncFailedException]Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb at org.teiid.adminapi.jboss.ManagedUtil.execute(ManagedUtil.java:295) at org.teiid.adminapi.jboss.ManagedUtil.deployArchive(ManagedUtil.java:235) at org.teiid.adminapi.jboss.ManagedUtil.deployArchive(ManagedUtil.java:222) at org.teiid.adminapi.jboss.Admin.deployVDB(Admin.java:184) 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.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:121) at org.teiid.jboss.deployers.RuntimeEngineDeployer$1.invoke(RuntimeEngineDeployer.java:246) ... 33 more Caused by: java.lang.RuntimeException: java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.transferDeployment(StreamingDeploymentTarget.java:286) at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.distribute(StreamingDeploymentTarget.java:106) at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.distribute(DeploymentProgressImpl.java:178) at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:83) at org.teiid.adminapi.jboss.ManagedUtil.execute(ManagedUtil.java:290) ... 42 more Caused by: java.io.SyncFailedException: Deployment content already exists: /home/psrna/data/jboss/soa-5.1.0.ER3-modeshape-2.3-teiid-7.1/jboss-as/server/default/deploy/MyFirstVDB.vdb at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.addDeploymentContent(BasicDeploymentRepository.java:177) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.handleStream(AbstractDeployHandler.java:288) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.handleStream(AbstractDeployHandler.java:63) at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1841) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:917) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:2034) at org.jboss.remoting.Client.invoke(Client.java:877) at org.jboss.remoting.Client.invoke(Client.java:1756) at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.transferDeployment(StreamingDeploymentTarget.java:277) ... 46 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-709) Problems with Operations Editor Input Variables Section behavior

by Barry LaFond (JIRA)

Problems with Operations Editor Input Variables Section behavior ---------------------------------------------------------------- Key: TEIIDDES-709 URL: https://jira.jboss.org/browse/TEIIDDES-709 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1.1 Reporter: Barry LaFond Assignee: Ted Jones Fix For: 7.1.1 Found a couple of behavior issues with Input Variables Section. 1) Selecting different Operations in tree on left, does not clear out input variables from previous selection. - If you select an interface, then re-select an operation the input variables seem to be correct. 2) Re-selecting an Operation after removing (de-selecting) input variables and SAVING re-adds the Input variables and dirties the model. - This should probably not auto-edit an operation's SQL and input variables just on selection. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-703) Teiid CP's created by "Execute VDB" actions should prompt for credentials rather than use the Admin credentials.

by John Doyle (JIRA)

Teiid CP's created by "Execute VDB" actions should prompt for credentials rather than use the Admin credentials. ---------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-703 URL: https://jira.jboss.org/browse/TEIIDDES-703 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1.1 The Admin credentials are used to deploy the VDB, as they should be, but then are then reused to create the ConnectionProfile to query the VDB. We should prompt the user to supply the credentials for the JDBC connection. -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-708) Migration of MMx MMR MetaData repository VDB produces many different errors in the log.

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-708?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIIDDES-708: --------------------------------- Priority: Critical (was: Major) > Migration of MMx MMR MetaData repository VDB produces many different errors in the log. > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-708 > URL: https://jira.jboss.org/browse/TEIIDDES-708 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Van Halbert > Priority: Critical > Attachments: Mmr_553.vdb > > > As part of migration of MMx metadata repository users, the old MMR vdb needs to be converted and usable to access the old repository thru Teiid. > When trying to convert the models, many errors are seen in the JBDS console, and 90% of the models have red x's. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-708) Migration of MMx MMR MetaData repository VDB produces many different errors in the log.

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-708?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-2580 to TEIIDDES-708: ------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-708 (was: SOA-2580) Affects Version/s: 7.1.1 (was: JBDS) Security: (was: Public) Component/s: Import/Export (was: Tooling) (was: EDS) > Migration of MMx MMR MetaData repository VDB produces many different errors in the log. > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-708 > URL: https://jira.jboss.org/browse/TEIIDDES-708 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Van Halbert > Attachments: Mmr_553.vdb > > > As part of migration of MMx metadata repository users, the old MMR vdb needs to be converted and usable to access the old repository thru Teiid. > When trying to convert the models, many errors are seen in the JBDS console, and 90% of the models have red x's. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-708) Migration of MMx MMR MetaData repository VDB produces many different errors in the log.

by Van Halbert (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-708?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIIDDES-708: --------------------------------- Attachment: Mmr_553.vdb attached is the 553 MMR.vdb > Migration of MMx MMR MetaData repository VDB produces many different errors in the log. > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-708 > URL: https://jira.jboss.org/browse/TEIIDDES-708 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1.1 > Reporter: Van Halbert > Attachments: Mmr_553.vdb > > > As part of migration of MMx metadata repository users, the old MMR vdb needs to be converted and usable to access the old repository thru Teiid. > When trying to convert the models, many errors are seen in the JBDS console, and 90% of the models have red x's. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-329) Operations Editor does not correctly wrap user-entered SQL with CREATE... and END

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-329?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-329: ---------------------------------- Assignee: Ted Jones Fix Version/s: 7.2 Affects Version/s: 7.1.1 > Operations Editor does not correctly wrap user-entered SQL with CREATE... and END > --------------------------------------------------------------------------------- > > Key: TEIIDDES-329 > URL: https://jira.jboss.org/browse/TEIIDDES-329 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1.1 > Environment: fedora 10, Designer build 3257 > Reporter: Paul Nittel > Assignee: Ted Jones > Fix For: 7.2 > > > I ran across this while running the E2E Updateable Web Service Test Script. > After creating the Web Service interface and initial steps of creating the InsertProduct operation, I pasted in the SQL. When I validated the SQL, the Designer wrapped it, beginning with the CREATE, and ending with END. Unfortunately, the terminating END is placed immedately after the END in the pasted in text. The validation then fails when it reaches the new word, "ENDEND". (the user needs to separate the "ENDEND" into "END END" and it will parse correctly. > The error message is: > The query is not parsable. > Parsing error: Encountered "<EOF>" at line 1, column 464. > Was expecting: > "=" ... > The SQL winds up being: > CREATE VIRTUAL PROCEDURE BEGIN DECLARE string VARIABLES.IN_ID = xpathvalue(ProductsWebSvc.ProdInterface.DeleteProduct.ProductIdIn, '/*:InstrIdInput/*:ID'); DECLARE integer VARIABLES.delete_count = 0; VARIABLES.DELETE_COUNT = DELETE FROM Updates.UpdateProduct WHERE Updates.UpdateProduct.INSTR_ID = VARIABLES.IN_ID; IF(VARIABLES.DELETE_COUNT = 1) BEGIN SELECT * FROM ProductDoc.goodResultsDocument; END ELSE BEGIN SELECT * FROM ProductDoc.badResultsDocument; ENDEND -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-347) NPE (unhandled event loop exception) when trying to build a sub-datatype (Simple Datatypes Editor)

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-347?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-347. ----------------------------------- Resolution: Duplicate Issue Same as TEIIDDES-612 which is fixed. > NPE (unhandled event loop exception) when trying to build a sub-datatype (Simple Datatypes Editor) > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-347 > URL: https://jira.jboss.org/browse/TEIIDDES-347 > Project: Teiid Designer > Issue Type: Task > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Attachments: SubTypeNpe.txt > > > I'm following the E2E XSD Simple Datatypes Editor Test Script... > To build a sub-type, I choose the Boolean built-in type then click the Create subtype of this Datatype hyperlink. The stack trace is attached. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-367) Allow SQLExplorer to connect to live servers and issue queries

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-367?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-367. --------------------------------- Assignee: Barry LaFond Resolution: Done SQL Explorer was removed from Designer for 7.0 Designer > Allow SQLExplorer to connect to live servers and issue queries > -------------------------------------------------------------- > > Key: TEIIDDES-367 > URL: https://jira.jboss.org/browse/TEIIDDES-367 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > Fix For: No Future > > > SQLExplorer is a better, more user-friendly, more full-featured test client than QueryBuilder. > The MMX server sometimes has access to things that client does not. > Connecting directly to servers does not require VDB execution overhead, and allows a more lightweight test client approach. > This might allow depreciation of QB. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-386) Add validation rule for missing names in source for physical tables

by Paul Nittel (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-386?page=com.atlassian.jira.plugin... ] Paul Nittel updated TEIIDDES-386: --------------------------------- Attachment: PartsByHand-ds.xml PartsNIS_MPS.zip > Add validation rule for missing names in source for physical tables > ------------------------------------------------------------------- > > Key: TEIIDDES-386 > URL: https://jira.jboss.org/browse/TEIIDDES-386 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Environment: All > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 7.2 > > Attachments: PartsByHand-ds.xml, PartsNIS_MPS.zip, wtf_parts_porsche.png > > > I created a physical model and added names in source for the columns, forgetting the table. It validates OK. I wired it to a connector binding and tried to preview the data. This failed with a rather verbose, ugly Oracle error. See attached screenshot. > Should/Can we add a new rule to validate the presence of all names in source for source models. > (Once I defined the tables NIS, it worked fine.) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2010