[JBoss JIRA] (TEIID-4197) Redshift - some comparison conditions are not supported with ANY, SOME and ALL
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4197?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4197:
----------------------------------
Component/s: JDBC Connector
> 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
> Components: JDBC Connector
> 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
[JBoss JIRA] (TEIID-4196) Redshift - function TO_TIMESTAMP does not exist
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4196?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4196.
-----------------------------------
Fix Version/s: 9.0
8.12.5
Resolution: Done
switched to the to_date function instead and removed the ability to support timezone parse/format. I couldn't find enough information to know if redshift in general can't support time component parsing, but that may also be needed.
> Redshift - function TO_TIMESTAMP does not exist
> -----------------------------------------------
>
> Key: TEIID-4196
> URL: https://issues.jboss.org/browse/TEIID-4196
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.x
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> During the translation of query, Teiid uses _TO\_TIMESTAMP_ function, but there is no such function in Redshift.
> *Example Queries:*
> SELECT IntKey, PARSETIMESTAMP(timestampvalue, 'yyyy-MM-dd HH:mm:ss') FROM Source.SmallA
> SELECT IntKey, PARSEDATE(datevalue, 'MMM-dd-yyyyGG') FROM Source.SmallA
> *Exception:*
> {code:plain}
> 12:52:37,566 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue124) TEIID30020 Processing exception for request tNdOaoYxZVoV.33 'TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.intkey, cast(TO_TIMESTAMP(to_char(g_0.datevalue, 'YYYY-MM-DD'), 'Mon-DD-YYYYAD') AS date) FROM smalla AS g_0]'. Originally TeiidProcessingException 'ERROR: Specified types or functions (one per INFO message) not supported on Redshift tables.' QueryExecutorImpl.java:2157.: org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.intkey, cast(TO_TIMESTAMP(to_char(g_0.datevalue, 'YYYY-MM-DD'), 'Mon-DD-YYYYAD') AS date) FROM smalla AS g_0]
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:401) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:470) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> 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: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.intkey, cast(TO_TIMESTAMP(to_char(g_0.datevalue, 'YYYY-MM-DD'), 'Mon-DD-YYYYAD') AS date) FROM smalla AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) [: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) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at com.sun.proxy.$Proxy47.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> 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) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> ... 6 more
> Caused by: org.postgresql.util.PSQLException: ERROR: Specified types or functions (one per INFO message) not supported on Redshift tables.
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4196) Redshift - function TO_TIMESTAMP does not exist
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4196?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4196:
----------------------------------
Component/s: JDBC Connector
> Redshift - function TO_TIMESTAMP does not exist
> -----------------------------------------------
>
> Key: TEIID-4196
> URL: https://issues.jboss.org/browse/TEIID-4196
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.x
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> During the translation of query, Teiid uses _TO\_TIMESTAMP_ function, but there is no such function in Redshift.
> *Example Queries:*
> SELECT IntKey, PARSETIMESTAMP(timestampvalue, 'yyyy-MM-dd HH:mm:ss') FROM Source.SmallA
> SELECT IntKey, PARSEDATE(datevalue, 'MMM-dd-yyyyGG') FROM Source.SmallA
> *Exception:*
> {code:plain}
> 12:52:37,566 WARN [org.teiid.PROCESSOR] (Worker12_QueryProcessorQueue124) TEIID30020 Processing exception for request tNdOaoYxZVoV.33 'TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.intkey, cast(TO_TIMESTAMP(to_char(g_0.datevalue, 'YYYY-MM-DD'), 'Mon-DD-YYYYAD') AS date) FROM smalla AS g_0]'. Originally TeiidProcessingException 'ERROR: Specified types or functions (one per INFO message) not supported on Redshift tables.' QueryExecutorImpl.java:2157.: org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.intkey, cast(TO_TIMESTAMP(to_char(g_0.datevalue, 'YYYY-MM-DD'), 'Mon-DD-YYYYAD') AS date) FROM smalla AS g_0]
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:401) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:470) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> 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: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0.intkey, cast(TO_TIMESTAMP(to_char(g_0.datevalue, 'YYYY-MM-DD'), 'Mon-DD-YYYYAD') AS date) FROM smalla AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) [: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) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at com.sun.proxy.$Proxy47.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> 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) [teiid-engine-8.12.5.redhat-4.jar:8.12.5.redhat-4]
> ... 6 more
> Caused by: org.postgresql.util.PSQLException: ERROR: Specified types or functions (one per INFO message) not supported on Redshift tables.
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157)
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886)
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4199) Redshift fails locate pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4199?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4199.
-----------------------------------
Resolution: Done
Used the standard substring in the locate handling for redshift compatibility.
> Redshift fails locate pushdown
> ------------------------------
>
> Key: TEIID-4199
> URL: https://issues.jboss.org/browse/TEIID-4199
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> The LOCATE(x,y,z) function translates incorrectly:
> Query: SELECT INTKEY, STRINGKEY FROM Source.SmallA WHERE LOCATE('1', STRINGKEY, 2) IN (1, 2)
> Source-specific command: SELECT g_0.intkey, g_0.stringkey FROM smalla AS g_0 WHERE (position('1' in substr(g_0.stringkey, 2)) + 1) IN (1, 2)
> Root exception message: Caused by: org.postgresql.util.PSQLException: ERROR: function SUBSTR does not exist (Hint: use SUBSTRING instead)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4200) Provide support for Wildfly 10
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4200:
-----------------------------------
Summary: Provide support for Wildfly 10
Key: TEIID-4200
URL: https://issues.jboss.org/browse/TEIID-4200
Project: Teiid
Issue Type: Feature Request
Components: Server
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 9.1
Upgrade the host runtime environment for Teiid Server to be WildFly 10.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4121) Enhancing the External Materialization
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-4121?page=com.atlassian.jira.plugin... ]
Kylin Soong reassigned TEIID-4121:
----------------------------------
Assignee: Kylin Soong (was: Steven Hawkins)
> Enhancing the External Materialization
> --------------------------------------
>
> Key: TEIID-4121
> URL: https://issues.jboss.org/browse/TEIID-4121
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 9.0
>
>
> The intention of move "status" table to physical database is to increase durable and fully control refresh and loading, but it increase the complexity.
> The "status" table by design should unique for whole VDB, if you look the https://teiid.gitbooks.io/documents/content/caching/External_Materializat..., the table structure:
> {code:sql}
> CREATE TABLE status
> (
> VDBName varchar(50) not null,
> VDBVersion integer not null,
> SchemaName varchar(50) not null,
> Name varchar(256) not null,
> TargetSchemaName varchar(50),
> TargetName varchar(256) not null,
> Valid boolean not null,
> LoadState varchar(25) not null,
> Cardinality long,
> Updated timestamp not null,
> LoadNumber long not null,
> PRIMARY KEY (VDBName, VDBVersion, SchemaName, Name)
> );
> {code}
> but currently, one VDB may have multiple "status" table, each view may have it's own "status" table. Further more, we can consider create status table automatically, which like internal, status create once VDB start, and configured in VDB scope.
> From finishedDeployment logic in MaterializationManager, MATERIALIZED_TABLE be used to determine whether the Mat is internal or external, But we lack the validation in metadata loading, in my previous test, the Internal Mat view configured lots of external view's properties like "status" table, the validation not throw excepton.
--
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 Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4194?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4194:
---------------------------------------
The initial design of the Informix translator did not expect a time type to be used, thus the default behavior of producing a full timestamp literal that represents the time. Adding support should not require too much effort.
> 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-4146) Using JDG Library Mode, unable to perform insert (
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4146?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4146:
------------------------------------------------
Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1327752|https://bugzilla.redhat.com/show_bug.cgi?id=1327752] from ON_QA to VERIFIED
> Using JDG Library Mode, unable to perform insert (
> --------------------------------------------------
>
> Key: TEIID-4146
> URL: https://issues.jboss.org/browse/TEIID-4146
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.5
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
> Fix For: 9.0, 8.12.5
>
>
> Trying to run the JDG local cache quickstart, get the following error when trying to perform an insert:
> 15:09:34,027 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue12) TEIID30020 Processing exception for request O25SlCY41bD5.6 'TEIID30492 Element StockCache.Stock.StockObject of StockCache.Stock is neither nullable nor has a default value. A value must be specified in the insert.'. Originally QueryValidatorException Request.java:330. Enable more detailed logging to see the entire stacktrace.
> The issue is because the StockObject column is set to be NullType.unknown, instead of NullType.Nullable. This is because the metadata processor in the translator-object is setting it incorrectly.
> Workaround:
> - Using Teiid Designer to import the source model and change the null type.
> - use dynamic vdb and define the DDL metadata to set the null type.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIID-4199) Redshift fails locate pushdown
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4199?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4199:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1296599
Bugzilla Update: Perform
> Redshift fails locate pushdown
> ------------------------------
>
> Key: TEIID-4199
> URL: https://issues.jboss.org/browse/TEIID-4199
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> The LOCATE(x,y,z) function translates incorrectly:
> Query: SELECT INTKEY, STRINGKEY FROM Source.SmallA WHERE LOCATE('1', STRINGKEY, 2) IN (1, 2)
> Source-specific command: SELECT g_0.intkey, g_0.stringkey FROM smalla AS g_0 WHERE (position('1' in substr(g_0.stringkey, 2)) + 1) IN (1, 2)
> Root exception message: Caused by: org.postgresql.util.PSQLException: ERROR: function SUBSTR does not exist (Hint: use SUBSTRING instead)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months