[JBoss JIRA] (TEIIDDES-2895) No warning after deleting schema and UDF Jars
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2895?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2895:
-----------------------------------
Fix Version/s: 11.2
(was: 11.0.2)
> No warning after deleting schema and UDF Jars
> ---------------------------------------------
>
> Key: TEIIDDES-2895
> URL: https://issues.jboss.org/browse/TEIIDDES-2895
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 10.0.1
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Fix For: 11.2
>
> Attachments: ScreenShot1.png, XmlStagingTableProject.zip
>
>
> There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema.
> Should be there some warning that schema was deleted and VDB should not be deploy on server without schema.
> EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (TEIIDDES-3036) Create POJO doesn't generate anything when one of the columns has a column type biginteger
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3036?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-3036 at 4/10/17 3:55 PM:
-----------------------------------------------------------------
So planned fix is to check for biginteger types and presenting an error dialog instead stating:
*Cannot generate POJO with column data type of biginteger*
*Change the column data type to long and re-launch this wizard.*
was (Author: blafond):
So planned fix is to check for biginteger types and presenting an error dialog instead stating:
*Cannot generate POJO with column data type of biginteger
Change the column data type to long and re-launch this wizard.*
> Create POJO doesn't generate anything when one of the columns has a column type biginteger
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3036
> URL: https://issues.jboss.org/browse/TEIIDDES-3036
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: JBoss Developer Studio 9.1.0 with Teiid Designer 10.0.2 installed
> Reporter: Cojan van Ballegooijen
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
> Attachments: Screen Shot 2017-02-09 at 12.02.56.png, create-pojo-datatype-warning.png
>
>
> Creating a POJO from a source model table doesn't generate the classes and module zip file when one of the columns has a datatype biginteger.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (TEIIDDES-3036) Create POJO doesn't generate anything when one of the columns has a column type biginteger
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3036?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3036:
----------------------------------------
So planned fix is to check for biginteger types and presenting an error dialog instead stating:
*Cannot generate POJO with column data type of biginteger
Change the column data type to long and re-launch this wizard.*
> Create POJO doesn't generate anything when one of the columns has a column type biginteger
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-3036
> URL: https://issues.jboss.org/browse/TEIIDDES-3036
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: JBoss Developer Studio 9.1.0 with Teiid Designer 10.0.2 installed
> Reporter: Cojan van Ballegooijen
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
> Attachments: Screen Shot 2017-02-09 at 12.02.56.png, create-pojo-datatype-warning.png
>
>
> Creating a POJO from a source model table doesn't generate the classes and module zip file when one of the columns has a datatype biginteger.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (TEIIDDES-2755) No Quick fix offered after importing VDB with same models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2755?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2755:
----------------------------------------
[~mmakovy] I took a look at this today. I imported and extracted models with Quick-fix and simple "Extract" on file system/refresh the project. In both cases, a lot of ERRORS were generated. How old is this VDB? We've also deprecated the XML Doc model, so wondering if the testing your use-case would better be served with smaller vdbs?
Also tested with VDB with simple source/view model. Second project showed the above behavior of not building/validating/generating the warning messages about the VDB's models not in workspace.
Managing multiple projects with duplicate EMF/XMI models is not a suggested workflow.. and I'd discourage it. If a user wants to "Save As" (i.e. clone) a model to another project and work with that, it should work fine. having duplicate UUID's (EMF objects) and XMI models being loaded into Eclipse is very risky.
> No Quick fix offered after importing VDB with same models
> ---------------------------------------------------------
>
> Key: TEIIDDES-2755
> URL: https://issues.jboss.org/browse/TEIIDDES-2755
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 11.0.2
>
> Attachments: QT_Greenplum_Push.vdb, QT_MySql50_Push.vdb, Screen Shot 2016-01-12 at 9.57.25 (2).png, Screen Shot 2016-01-12 at 9.57.48 (2).png, Screen Shot 2016-01-12 at 9.58.00 (2).png
>
>
> I have 2 VDBs with models that have same names. After importing the first one and extracting the models, TD doesn't offer this option for the second VDB in second project.
> I can see that the warning says that models are not in +workspace+, but I think TD should check if models are in the +project folder+ not in workspace.
> In the screenshots, you can see that there is no warning for NewProject2.
> VDBs attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[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 reassigned TEIIDDES-2793:
--------------------------------------
Assignee: Paul Richardson (was: Barry LaFond)
> 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.2
>
> 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)
7 years, 1 month