[JBoss JIRA] (TEIID-3501) IN clause - teradata does not support "CAST( ... AS ...)" statement in "IN(...)"
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3501?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3501:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1226824|https://bugzilla.redhat.com/show_bug.cgi?id=1226824] from ON_QA to VERIFIED
> IN clause - teradata does not support "CAST( ... AS ...)" statement in "IN(...)"
> --------------------------------------------------------------------------------
>
> Key: TEIID-3501
> URL: https://issues.jboss.org/browse/TEIID-3501
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1.6_2
> Environment: teradata version: 15
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 8.12, 8.11.2
>
>
> The teradata DB does not support CAST statement in IN. Query (1), teradata exception (2), source specific command (3), query that teradata accepts (4).
> (1) SELECT BQT1.SmallA.IntKey FROM BQT1.SmallA WHERE BQT1.SmallA.TimeStampValue IN (convert('2000-01-01 00:00:12.0', timestamp), convert('2000-01-01 00:00:45.0', timestamp)) ORDER BY IntKey
> (2) SELECT g_0.intkey AS c_0 FROM smalla AS g_0 WHERE g_0.timestampvalue IN (cast('2000-01-01 00:00:12.0' AS TIMESTAMP(6)), cast('2000-01-01 00:00:45.0' AS TIMESTAMP(6))) ORDER BY 1
> (3) SELECT g_0.intkey AS c_0 FROM smalla AS g_0 WHERE g_0.timestampvalue IN ('2000-01-01 00:00:12.0', '2000-01-01 00:00:45.0') ORDER BY 1
> (4) Caused by: java.sql.SQLException: [Teradata Database] [TeraJDBC 15.10.00.05] [Error 3706] [SQLState 42000] Syntax error: expected something between ')' and ','.
> at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDatabaseSQLException(ErrorFactory.java:308)
> ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-3345) NPE while accessing VDB via OData access
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3345?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3345:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1194292|https://bugzilla.redhat.com/show_bug.cgi?id=1194292] from ON_QA to VERIFIED
> NPE while accessing VDB via OData access
> ----------------------------------------
>
> Key: TEIID-3345
> URL: https://issues.jboss.org/browse/TEIID-3345
> Project: Teiid
> Issue Type: Bug
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Priority: Minor
> Labels: Alpha1
> Fix For: 8.11
>
>
> If wrong odata URL is provided, an internal error is displayed:
> URL: http://localhost:8080/odata/
> Exception: org.teiid.core.TeiidRuntimeException: TEIID16008 VDB name not defined on the URL. The url format is http://{host}:{port}/odata/{vdb-name}[.{vdb-version}]/...
> org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:88)
> org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:47)
> ....
> This behavior is quite expected.
> URL: http://localhost:8080/odata
> Exception: java.lang.NullPointerException
> org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:80)
> org.teiid.odata.TeiidProducerProvider.getContext(TeiidProducerProvider.java:47)
> ...
> I expect that teiid should return similar exception
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4094) Move the packaging of teiid-jdbc.jar into is own project
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4094?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4094:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1318684|https://bugzilla.redhat.com/show_bug.cgi?id=1318684] from ON_QA to VERIFIED
> Move the packaging of teiid-jdbc.jar into is own project
> --------------------------------------------------------
>
> Key: TEIID-4094
> URL: https://issues.jboss.org/browse/TEIID-4094
> Project: Teiid
> Issue Type: Enhancement
> Components: Build/Kits
> Affects Versions: 8.12.x
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.12.5
>
>
> The issue with the way the teiid-jdbc.jar is packaged now, is that the teiid-web-console.zip gets included as a dependency.
> {code}
> [INFO] +- org.jboss.teiid:teiid:jar:jdbc:8.12.5.redhat-2:compile
> [INFO] | \- org.jboss.teiid.web-console:teiid-console-dist:zip:jboss-as7:2.5.6.Final-redhat-63-4:compile
> {code}
> And that becomes an issue when other external projects to Teiid include the jdbc driver as a dependency, in that they also end up requiring the web-console.zip.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4080) Prevent expired client/server certificates from being accepted
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4080?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4080:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1318154|https://bugzilla.redhat.com/show_bug.cgi?id=1318154] from ON_QA to VERIFIED
> Prevent expired client/server certificates from being accepted
> --------------------------------------------------------------
>
> Key: TEIID-4080
> URL: https://issues.jboss.org/browse/TEIID-4080
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
> Attachments: keystore_client.jks, keystore_server_root_expired.jks, truststore.jks, truststore_expired.jks
>
>
> If SSL is enabled (1-way or 2-way) server provides to the client certificate which must be signed by valid certificate of trusted CA.
> If server provides certificate which is signed by certificate of root CA which already expired client accepts this certificate. Client should not accept such certificate.
> This affects 1-way and 2-way authentication modes.
> On the client side, paths are set using teiid-specific properties:
> {code:java}
> System.setProperty("org.teiid.ssl.keyStore", clientKeystorePath);
> System.setProperty("org.teiid.ssl.keyStorePassword", "keystorepswd");
> System.setProperty("org.teiid.ssl.keyAlias", "client");
> System.setProperty("org.teiid.ssl.keyPassword", "keystorepswd");
> System.setProperty("org.teiid.ssl.trustStore", clientTruststorePath);
> System.setProperty("org.teiid.ssl.trustStorePassword", "truststorepswd");
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4031) Missing dependency in module com.fasterxml.jackson.dataformat.yaml
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4031?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4031:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1315597|https://bugzilla.redhat.com/show_bug.cgi?id=1315597] from ON_QA to VERIFIED
> Missing dependency in module com.fasterxml.jackson.dataformat.yaml
> ------------------------------------------------------------------
>
> Key: TEIID-4031
> URL: https://issues.jboss.org/browse/TEIID-4031
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.5
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.2
>
>
> Module "com.fasterxml.jackson.dataformat.yaml" is missing dependency "com.fasterxml.jackson". Due to this error user cannot see swagger metadata in yaml format.
> Exception:
> {code:text}
> 08:53:02,970 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/rest_1].[default]] (http-/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet default threw exception: org.jboss.resteasy.spi.UnhandledException: java.lang.LinkageError: Failed to link com/fasterxml/jackson/dataformat/yaml/YAMLFactory (Module "com.fasterxml.jackson.dataformat.yaml:main" from local module loader @65693ccc (finder: local module finder @6016a917 (roots: /home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/dv,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/base)))
> at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:367) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:235) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:211) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:576) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:543) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invokePropagateNotFound(SynchronousDispatcher.java:171) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:212) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.plugins.server.servlet.FilterDispatcher.doFilter(FilterDispatcher.java:59) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0-internal]
> Caused by: java.lang.LinkageError: Failed to link com/fasterxml/jackson/dataformat/yaml/YAMLFactory (Module "com.fasterxml.jackson.dataformat.yaml:main" from local module loader @65693ccc (finder: local module finder @6016a917 (roots: /home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/dv,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/base)))
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:487) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:277) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:92) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.Module.loadModuleClass(Module.java:568) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at io.swagger.jaxrs.listing.ApiListingResource.getListingYaml(ApiListingResource.java:150) [swagger-jaxrs-1.5.2.jar:1.5.2]
> at io.swagger.jaxrs.listing.ApiListingResource.getListing(ApiListingResource.java:114) [swagger-jaxrs-1.5.2.jar:1.5.2]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0-internal]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0-internal]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0-internal]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0-internal]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:168) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:561) [resteasy-jaxrs-2.3.12.Final-redhat-1.jar:]
> ... 18 more
> Caused by: java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/JsonFactory
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0-internal]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0-internal]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:361) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:482) [jboss-modules.jar:1.3.7.Final-redhat-1]
> ... 37 more
> Caused by: java.lang.ClassNotFoundException: com.fasterxml.jackson.core.JsonFactory from [Module "com.fasterxml.jackson.dataformat.yaml:main" from local module loader @65693ccc (finder: local module finder @6016a917 (roots: /home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/dv,/home/jdurani/redhat/data-virtualization/dv_6.3.0/jboss-eap-6.4/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.7.Final-redhat-1]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.7.Final-redhat-1]
> ... 41 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-3022) refine removed vdb handling
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3022?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3022:
------------------------------------------------
Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1291719|https://bugzilla.redhat.com/show_bug.cgi?id=1291719] from ON_QA to VERIFIED
> refine removed vdb handling
> ---------------------------
>
> Key: TEIID-3022
> URL: https://issues.jboss.org/browse/TEIID-3022
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 8.1
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> With TEIID-2105 the server will reject requests against a non-active vdb, which includes a removed vdb. This is against the original intent of allowing for lazy cleanup. We should either have a vdb remove proactively terminate all sessions and fully cleanup or we should reinstate the lazy logic. At this point it probably makes the most sense to go the first route as there is other logic (materialization management for one) now checking the vdb state and assuming that removal will invalidate the vdb.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4194) Informix translator - constant time values are translated as timestamp
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4194?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4194:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1334201
Bugzilla Update: Perform
> Informix translator - constant time values are translated as timestamp
> ----------------------------------------------------------------------
>
> Key: TEIID-4194
> URL: https://issues.jboss.org/browse/TEIID-4194
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.12.x
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Teiid translates constant time value (e.g. '02:00:00') as a _timestamp_ (\{ts '1970-01-01 02:00:00'\}) even if column is of type _time_.
> *DDL:*
> {code:xml}
> <model name="Source" type="PHYSICAL">
> ...
> <metadata type="DDL">
> <![CDATA[
> CREATE FOREIGN TABLE SmallA (
> ...
> TimeValue time OPTIONS (NATIVE_TYPE 'datetime hour to fraction(1)', NAMEINSOURCE 'timevalue'),
> ...
> {code}
> *Example query:*
> {code:sql}SELECT TimeValue FROM Source.SmallA WHERE TimeValue > '21:00:00' OR TimeValue < '02:00:00'{code}
> *Source-specific command:*
> {code:sql}SELECT g_0.timevalue FROM smalla AS g_0 WHERE g_0.timevalue > {ts '1970-01-01 21:00:00.0'} OR g_0.timevalue < {ts '1970-01-01 02:00:00.0'}{code}
> *Exception:*
> {code:plain}
> 09:08:35,320 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue65) Connector worker process failed for atomic-request=c/y8mqFekM4p.9.1.4: org.teiid.translator.jdbc.JDBCExecutionException: -1261 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.timevalue FROM smalla AS g_0 WHERE g_0.timevalue > {ts '1970-01-01 21:00:00.0'} OR g_0.timevalue < {ts '1970-01-01 02:00:00.0'}]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_40]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_40]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_40]
> at java.lang.reflect.Method.invoke(Method.java:497) [rt.jar:1.8.0_40]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy47.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> 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) [rt.jar:1.8.0_40]
> 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) [rt.jar:1.8.0_40]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]
> Caused by: java.sql.SQLException: Too many digits in the first field of datetime or interval.
> at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:408)
> at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3178)
> at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3458)
> at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2369)
> at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2294)
> at com.informix.jdbc.IfxSqli.executePrepare(IfxSqli.java:1264)
> at com.informix.jdbc.IfxPreparedStatement.setupExecutePrepare(IfxPreparedStatement.java:308)
> at com.informix.jdbc.IfxPreparedStatement.processSQL(IfxPreparedStatement.java:289)
> at com.informix.jdbc.IfxPreparedStatement.<init>(IfxPreparedStatement.java:182)
> at com.informix.jdbc.IfxSqliConnect.createPreparedStmt(IfxSqliConnect.java:6108)
> at com.informix.jdbc.IfxSqliConnect.prepareStatement(IfxSqliConnect.java:2509)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:744)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:730)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:405)
> at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:196) [translator-jdbc-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:121) [translator-jdbc-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> ... 18 more
> Caused by: java.sql.SQLException
> at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:408)
> at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3463)
> ... 31 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4192) If a column is blank the TEXTAGG function excludes it from the output
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4192?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4192.
-----------------------------------
Fix Version/s: 9.0
8.12.5
8.13.5
Resolution: Done
Simply omitting the value, but not the separator.
> If a column is blank the TEXTAGG function excludes it from the output
> ----------------------------------------------------------------------
>
> Key: TEIID-4192
> URL: https://issues.jboss.org/browse/TEIID-4192
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.5.6_2
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.5
>
>
> If a column value is blank, it is excluding it in the result, causing incorrect output.
> TEXTAGG(FOR Last_Name,
> First_Name,
> Middle_initial,
> Currency_Code
> DELIMITER '|' QUOTE '"'
> )
> In the above example, if middle name is blank, then it should still show one empty column with "|" delimiter as shown below.
> Steigner|Debbie||USD
> But it returns output as excluding middle name since it is blank.
> Steigner|Debbie|USD
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4197) Redshift - some comparison conditions are not supported with ANY, SOME and ALL
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-4197:
-----------------------------------
Summary: Redshift - some comparison conditions are not supported with ANY, SOME and ALL
Key: TEIID-4197
URL: https://issues.jboss.org/browse/TEIID-4197
Project: Teiid
Issue Type: Bug
Affects Versions: 8.12.x
Reporter: Juraj Duráni
Assignee: Steven Hawkins
Some comparison conditions are not supported in Redshift with ANY, SOME and ALL.
*ALL:*
_Query:_ SELECT INTKEY FROM Source.SMALLA WHERE INTKEY > ALL (SELECT INTKEY FROM Source.SMALLA WHERE INTKEY < 45)
_Exception message:_ Caused by: org.postgresql.util.PSQLException: ERROR: ALL with <, >, <=, >=, or = comparison condition is not supported
*ANY:*
_Query:_ SELECT INTKEY FROM Source.SMALLA WHERE INTKEY > ANY (SELECT INTKEY FROM Source.SMALLA WHERE INTKEY < 45)
_Exception message:_ Caused by: org.postgresql.util.PSQLException: ERROR: ANY or SOME with <, >, <=, >=, <>, or != comparison condition is not supported
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months