July 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-3087: --------------------------------------- If you open up the .vdb file and look at the vdb.xml, all the properties are written in this manner. Hope the change does this for them all. > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.2 > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1980) Need support to create XA datasource

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1980?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1980: ----------------------------------- Fix Version/s: 11.2 (was: 11.0.2) > Need support to create XA datasource > ------------------------------------ > > Key: TEIIDDES-1980 > URL: https://issues.jboss.org/browse/TEIIDDES-1980 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.7, 11.0.1 > Reporter: Hisanobu Okuda > Assignee: Barry LaFond > Fix For: 11.2 > > > You can create non-XA (local-tx) datasource by right-clicking source model and select "Modeling>Create Data Source" in Teiid Designer. It needs to support to create XA data sources. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3085) Importer is not setting Name In Source for salesforce relationship name

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3085?page=com.atlassian.jira.plu... ] Debbie Steigner commented on TEIIDDES-3085: ------------------------------------------- [~blafond] Ok, if we can't set it then the customer will just need to continue to manually enter it. > Importer is not setting Name In Source for salesforce relationship name > ----------------------------------------------------------------------- > > Key: TEIIDDES-3085 > URL: https://issues.jboss.org/browse/TEIIDDES-3085 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.3 > > > Salesforce importer doesn't set Name in Source for relationship name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3085) Importer is not setting Name In Source for salesforce relationship name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3085?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3085: ---------------------------------------- [~dsteigne] Assuming this SF model was generated by the SF import wizard, it appears that when Designer constructs a relationship (aka Foreign Key), it's finding the parent table of the relationship and using that info to find the primary table and adding the FK to it. The relationship's *child table* is used as the *foreign* table reference. Note that the imported Data Model does not have a NIS property in it, so it's not available to set on the relationship. Not sure we can set this. > Importer is not setting Name In Source for salesforce relationship name > ----------------------------------------------------------------------- > > Key: TEIIDDES-3085 > URL: https://issues.jboss.org/browse/TEIIDDES-3085 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.3 > > > Salesforce importer doesn't set Name in Source for relationship name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3085) Importer is not setting Name In Source for salesforce relationship name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3085?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3085: ----------------------------------- Fix Version/s: 11.0.3 (was: 11.0.2) > Importer is not setting Name In Source for salesforce relationship name > ----------------------------------------------------------------------- > > Key: TEIIDDES-3085 > URL: https://issues.jboss.org/browse/TEIIDDES-3085 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.3 > > > Salesforce importer doesn't set Name in Source for relationship name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1810) Support larger statistic values

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1810: ----------------------------------- Fix Version/s: 11.0.3 (was: 11.0.2) > Support larger statistic values > ------------------------------- > > Key: TEIIDDES-1810 > URL: https://issues.jboss.org/browse/TEIIDDES-1810 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Dan Florian > Fix For: 11.0.3 > > > The table/column stats are currently limited to max int (2^31 -1) values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2793) Invalid conversion from type class org.teiid.core.types.BinaryType to type class java.lang.String

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2793?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2793: ----------------------------------- Fix Version/s: 11.0.3 (was: 11.0.2) > Invalid conversion from type class org.teiid.core.types.BinaryType to type class java.lang.String > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2793 > URL: https://issues.jboss.org/browse/TEIIDDES-2793 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 10.0 > Reporter: Matus Makovy > Assignee: Paul Richardson > Priority: Critical > Fix For: 11.0.3 > > Attachments: LDAP.zip > > > I think this is a server issue since it only occurs with DV 6.3.DR3 and with DV 6.2.2 is everything ok. > During LDAP import using Teiid Designer I ran into this exception: > {code:java} > org.teiid.jdbc.TeiidSQLException: TEIID10076 Invalid conversion from type class org.teiid.core.types.BinaryType with value '7B535348417D61396A315A6B4F7761527A5142376C714437726551336D362B6E446B5468674F5848714F48673D3D' to type class java.lang.String > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:703) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:542) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:268) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:306) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98) > at com.sun.proxy.$Proxy72.read(Unknown Source) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:405) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:551) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:404) > at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:338) > at org.jboss.tools.teiid.reddeer.connection.TeiidJDBCHelper.executeQuery(TeiidJDBCHelper.java:79) > at org.jboss.tools.teiid.reddeer.connection.TeiidJDBCHelper.isQuerySuccessful(TeiidJDBCHelper.java:111) > at org.jboss.tools.teiid.ui.bot.test.TeiidBot.simulatePreview(TeiidBot.java:276) > at org.jboss.tools.teiid.ui.bot.test.LdapImportTest.ldapImport(LdapImportTest.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.reddeer.junit.internal.runner.statement.RunTestMethod.evaluate(RunTestMethod.java:36) > at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69) > at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeTestExtensions.evaluate(RunIBeforeTestExtensions.java:63) > at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58) > at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:51) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:165) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:69) > at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:35) > at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:60) > at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:58) > at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:34) > at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:48) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:146) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:58) > at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:115) > at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.teiid.core.types.TransformationException: TEIID10076 Invalid conversion from type class org.teiid.core.types.BinaryType with value '7B535348417D61396A315A6B4F7761527A5142376C714437726551336D362B6E446B5468674F5848714F48673D3D' to type class java.lang.String > at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:940) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.correctTypes(ConnectorWorkItem.java:572) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:435) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:226) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy136.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ... 1 more > {code} > Exception occurred after I created VDB, deployed it and tried to query it with this query: > {code:sql} > select * from "LdapImp"."ou=people" > {code} > Project from Teiid Designer is attached. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2936) SQL generated from remote XML file template has wrong number of parameters

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2936?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2936: ----------------------------------- Fix Version/s: 11.0.3 (was: 11.0.2) > SQL generated from remote XML file template has wrong number of parameters > --------------------------------------------------------------------------- > > Key: TEIIDDES-2936 > URL: https://issues.jboss.org/browse/TEIIDDES-2936 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 10.0.1 > Reporter: stanislav kaleta > Priority: Optional > Fix For: 11.0.3 > > > Creating table with _+XML File - URL Source+_ template generates table with transformation SQL which contains error: > _ERROR: org.teiid.runtime.client.TeiidClientException: TEIID30140 Incorrect number of parameters specified on the stored procedure 3 - expected between 4 and 5 but got 3_ > part of SQL which contains error: (EXEC SourceModel.invokeHttp('GET', null, 'http://www.w3schools.com/xml/plant_catalog.xml')) AS f > Note: using Import Model Wizard, part of SQL is as follows: (EXEC SourceModel.invokeHttp('GET', null, 'http://www.w3schools.com/xml/plant_catalog.xml', 'TRUE')) AS f > In my opinion, template is missing _stream_ parameter from _invokeHttp_ procedure,... or is there any reason why it is not there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3092) Extension models imported from runtime are not properly setting the namespace URL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3092?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3092. ------------------------------------ Resolution: Done 11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/170a7697fd3c48df1... fixed in conjunction with TEIIDDES-3084 > Extension models imported from runtime are not properly setting the namespace URL > --------------------------------------------------------------------------------- > > Key: TEIIDDES-3092 > URL: https://issues.jboss.org/browse/TEIIDDES-3092 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.0.2 > > > Working on testing the infinispan-hotrod translator, the resulting imported extension model namepsace URL was set to 2014 version. Turns out this is hardcoded. > The translator properties are prefixed with the URL, so should discover this value for each extension model and set properly. > see MxdConverter.java class -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2939) Add module dependencies to support JDG 7.1 when Pojo is reversed engineered

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2939?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2939: --------------------------------------- For optimal usability, it needs to support the old (above) and the new, simpler method for only JDG 7.1 support. > Add module dependencies to support JDG 7.1 when Pojo is reversed engineered > --------------------------------------------------------------------------- > > Key: TEIIDDES-2939 > URL: https://issues.jboss.org/browse/TEIIDDES-2939 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 11.0.2 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2017