[JBoss JIRA] (TEIID-4313) use consistent ordering for group collectors
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4313:
-------------------------------------
Summary: use consistent ordering for group collectors
Key: TEIID-4313
URL: https://issues.jboss.org/browse/TEIID-4313
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1
In comparing older debug plans we see erroneous differences in the groups of plannodes depending upon the JRE since we're not using linked hashsets to hold the groups.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIID-4312) INNER and LEFT joins of CTEs fail or return incorrect results
by Salvatore R (JIRA)
Salvatore R created TEIID-4312:
----------------------------------
Summary: INNER and LEFT joins of CTEs fail or return incorrect results
Key: TEIID-4312
URL: https://issues.jboss.org/browse/TEIID-4312
Project: Teiid
Issue Type: Bug
Reporter: Salvatore R
Assignee: Steven Hawkins
I defined a table "test_a" with the same data and structure in PostgreSQL and MySQL:
{code:sql}
CREATE TABLE test_a(a integer, b integer);
INSERT INTO test_a VALUES (1, 1);
INSERT INTO test_a VALUES (1, 2);
INSERT INTO test_a VALUES (2, 1);
INSERT INTO test_a VALUES (2, 2);
INSERT INTO test_a VALUES (3, 2);
INSERT INTO test_a VALUES (3, 10);
{code}
The following query, based on the table in *PostgreSQL*, fails:
{code:sql}
with
CTE1 as (
WITH
CTE11 as (SELECT a from pg.test_a),
CTE21 as (select t1.a from CTE11 t1 join CTE11 t2 on t1.a=t2.a),
CTE31 as (select a from CTE21)
SELECT CTE31.a FROM CTE21 join CTE31 on CTE31.a=CTE21.a
)
select * from CTE1
{code}
with this exception:
{code:sql}
16:36:28,752 WARN [org.teiid.CONNECTOR] (Worker13_QueryProcessorQueue114) eYLiZgMIChSF Connector worker process failed for atomic-request=eYLiZgMIChSF.11.2.24: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH CTE11 (a) AS (SELECT NULL FROM "public"."test_a" AS g_0), CTE21 (a) AS (SELECT g_0.a FROM CTE11 AS g_0, CTE11 AS g_1 WHERE g_0.a = g_1.a) SELECT g_1.a FROM CTE21 AS g_0, CTE21 AS g_1 WHERE g_1.a = g_0.a]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
at com.sun.proxy.$Proxy56.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:262)
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:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.postgresql.util.PSQLException: ERROR: failed to find conversion function from unknown to text
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:504)
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
... 17 more
{code}
The same query based on the table in *MySQL* wrongly returns an empty result.
The main differences is that the query is fully pushed down to PostgreSQL but it isn't in MySQL.
Regarding wrong results, I am also experiencing a similar problem with the following query:
{code:sql}
with
CTE1 as (
WITH
alias as (SELECT a from pg.test_a),
alias2 as (select t2.a as a1, t1.a from alias t1 join (SELECT 1 as a) t2 on t1.a=t2.a),
CTE31 as (select t2.a as a1 from alias2 t2)
SELECT CTE31.a1 FROM alias2 join CTE31 on CTE31.a1=alias2.a
),
CTE2 as (
WITH
alias as (SELECT 1 as a),
alias2 as (select t2.a a1, t1.a from alias t1 join (SELECT 1 as a) t2 on t1.a=t2.a),
CTE32 as (select t2.a from alias2 t2)
SELECT CTE32.a FROM alias2 join CTE32 on CTE32.a=alias2.a
)
select * from CTE1 as T1 join CTE2 as T2 on T1.a1=T2.a
{code}
It returns 4 rows (as expected) if based on MySQL table but it returns 16 rows if pushed down to PostgreSQL.
I don't know if the two behaviors are related or not, but I can create a different ticket for the second issue, if needed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIID-4283) External Materialization interleaving loads SYSADMIN.loadMatView
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4283?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4283:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1348466|https://bugzilla.redhat.com/show_bug.cgi?id=1348466] from MODIFIED to ON_QA
> External Materialization interleaving loads SYSADMIN.loadMatView
> ----------------------------------------------------------------
>
> Key: TEIID-4283
> URL: https://issues.jboss.org/browse/TEIID-4283
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.5
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 9.1, 8.12.5, 9.0.1
>
> Attachments: jdg-log.txt
>
>
> There is a possibility of two concurrent loads of single materialized view when using SYSADMIN.loadMatView function. I observed the issue while:
> # Waiting for ttl-driven reload and in right time I triggered another load explicitly by invoking the loadMatView function.
> # Invoking SYSADMIN.loadMatView function multiple times in quick succession.
> The view definition:
> {code:sql}
> CREATE VIEW external_long_ttl (
> customer_id integer NOT NULL,
> total_amount integer
> ) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'FALSE',
> MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view',
> "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
> "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable',
> "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;',
> "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table ${db.table.prefix}dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_stage TO ${db.table.prefix}dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view TO ${db.table.prefix}dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE ${db.table.prefix}dv_matviews_mat_view_temp TO ${db.table.prefix}dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';',
> "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT',
> "teiid_rel:MATVIEW_TTL" 20000)
> AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;
> {code}
> Query to explicitly load the view:
> {code:sql}
> exec SYSADMIN.loadMatView(schemaName=>'View',viewname=>'external_long_ttl', invalidate=>'true')
> {code}
> I attached a log which starts with ttl-driven load, then the explicit load is performed. The issue noticed is in teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT , where primary and staging tables are being swapped. The second load (explicit) can't find the original table, as the ttl-driven load had already renamed it.
> But this situation of two concurrent loads should never occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3929:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1301527|https://bugzilla.redhat.com/show_bug.cgi?id=1301527] from MODIFIED to ON_QA
> Accumulo does not return null values
> ------------------------------------
>
> Key: TEIID-3929
> URL: https://issues.jboss.org/browse/TEIID-3929
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Fix For: 9.0, 8.12.5
>
>
> Accumulo doesn't return null values when a whole 'column' is being selected.
> For a command in accumulo shell like:
> {code:plain}
> scan -c name:BYTENUM
> {code}
> Accumulo returns only non-empty values, this is expected behaviour.
> Equivalent query in Teiid would be:
> {code:sql}
> SELECT ByteNum FROM SmallA
> {code}
> Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIID-4237) INNER JOIN returns incorrect results
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4237?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4237:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1341763|https://bugzilla.redhat.com/show_bug.cgi?id=1341763] from MODIFIED to ON_QA
> INNER JOIN returns incorrect results
> ------------------------------------
>
> Key: TEIID-4237
> URL: https://issues.jboss.org/browse/TEIID-4237
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 9.0, 8.7.6, 8.12.5, 8.7.7.6_2, 8.13.5
>
>
> Running the following query:
> {code:sql}
> select avg(t1.a) from
> (select 3 as a, 3 as b union all
> select 1 as a, 1 as b union all
> select 3 as a, 3 as b) as t1
> join (select 1 as a, 1 as b union all
> select 1 as a, 1 as b union all
> select 2 as a, 2 as b union all
> select 2 as a, 2 as b union all
> select 3 as a, 3 as b union all
> select 3 as a, 3 as b) as t2 on t1.a=t2.a
> {code}
> on teiid causes incorrect result: 2 in comparing with mysql which returns 2.333.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIID-4287) An exception is thrown by PostgreSQL when nested CTEs are pushed down
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4287?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4287:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1349030|https://bugzilla.redhat.com/show_bug.cgi?id=1349030] from MODIFIED to ON_QA
> An exception is thrown by PostgreSQL when nested CTEs are pushed down
> ---------------------------------------------------------------------
>
> Key: TEIID-4287
> URL: https://issues.jboss.org/browse/TEIID-4287
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Salvatore R
> Assignee: Steven Hawkins
> Fix For: 9.1, 8.12.5, 8.13.6, 9.0.1
>
>
> I defined the following views in my VDB, based on a table in PostgreSQL:
> {code:sql}
> create view tv0 as
> WITH
> cte1 as (SELECT 1 as a),
> alias2 as (select a from cte1),
> cte3 as (select a from alias2)
> SELECT cte3.a FROM alias2 join cte3 on cte3.a=alias2.a;
> create view tv1 as
> WITH
> cte1 as (SELECT a from pg.test_a),
> alias2 as (select a from cte1),
> cte3 as (select a from alias2)
> SELECT cte3.a FROM alias2 join cte3 on cte3.a=alias2.a;
> create view tv2 as
> WITH
> alias2 as (select b, a from pg.test_a),
> cte4 as (select a from alias2)
> SELECT cte4.a FROM cte4 join alias2 on cte4.a=alias2.a ;
> {code}
> The following query, based on views tv0 and tv1:
> {code:sql}
> with
> CTE1 as (
> select a from (
> with CTE11 as (select a from views.tv0)
> select a from CTE11
> ) as SUBQ1),
> CTE2 as (
> select a from (
> with CTE21 as (select a from views.tv1)
> select a from CTE21
> ) as SUBQ2)
> select * from CTE1 as T1 join CTE2 as T2 on T1.a=T2.a
> {code}
> throws this exception:
> {code:sql}
> 18:55:23,260 WARN [org.teiid.PROCESSOR] (Worker24_QueryProcessorQueue773) qPWXuJPW78go TEIID30020 Processing exception for request qPWXuJPW78go.3 'TEIID30504 test_tables_pg: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH alias2__1 (a) AS (SELECT g_0."a" FROM "public"."test_a" AS g_0) SELECT g_1.a AS c_0 FROM alias2__1 AS g_0, alias2 AS g_1 WHERE g_1.a = g_0.a AND g_1.a = 1 ORDER BY c_0]'. Originally TeiidProcessingException 'ERROR: Relation "alias2" does not exist
> Position: 113' QueryExecutorImpl.java:2157. Enable more detailed logging to see the entire stacktrace.
> 19:00:13,379 WARN [org.teiid.CONNECTOR] (Worker28_QueryProcessorQueue775) qPWXuJPW78go Connector worker process failed for atomic-request=qPWXuJPW78go.4.7.144: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH alias2__1 (a) AS (SELECT g_0."a" FROM "public"."test_a" AS g_0) SELECT g_1.a AS c_0 FROM alias2__1 AS g_0, alias2 AS g_1 WHERE g_1.a = g_0.a AND g_1.a = 1 ORDER BY c_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy56.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:262)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.postgresql.util.PSQLException: ERROR: Relation "alias2" does not exist
> Position: 113
> 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:504)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
> ... 17 more
> {code}
> A similar query based on view tv2, throws a different exception:
> {code:sql}
> with
> CTE1 as (
> select a from (
> with CTE11 as (select a from views.tv2)
> select a from CTE11
> ) as SUBQ1),
> CTE2 as (
> select a from (
> with CTE21 as (select a from views.tv2)
> select a from CTE21
> ) as SUBQ2)
> select * from CTE1 as T1 join CTE2 as T2 on T1.a=T2.a
> {code}
> {code:sql}
> 19:05:02,784 WARN [org.teiid.CONNECTOR] (Worker30_QueryProcessorQueue778) qPWXuJPW78go Connector worker process failed for atomic-request=qPWXuJPW78go.5.2.145: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH alias2 (b, a) AS (SELECT NULL, g_0."a" FROM "public"."test_a" AS g_0), alias2__1 (a, b) AS (SELECT NULL, g_0."a" FROM "public"."test_a" AS g_0) SELECT g_2.a, g_0.a FROM alias2 AS g_0, alias2 AS g_1, alias2 AS g_2, alias2__1 AS g_3 WHERE g_2.a = g_3.a AND g_0.a = g_1.a AND g_0.a = g_2.a]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365)
> at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy56.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:262)
> 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:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.postgresql.util.PSQLException: ERROR: failed to find conversion function from unknown to integer
> 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:504)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (TEIID-4273) With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4273?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-4273:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1347311|https://bugzilla.redhat.com/show_bug.cgi?id=1347311] from MODIFIED to ON_QA
> With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-4273
> URL: https://issues.jboss.org/browse/TEIID-4273
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1, 8.12.5, 8.7.7.6_2, 9.0.1
>
>
> A query such as:
> WITH qry_0 as /\*+ no_inline */ (SELECT e2 AS a1, e1 as str FROM pm1.g1 AS t), qry_1 as /\*+ no_inline */ (SELECT 'b' AS a1) select (select a1 || 'a' from qry_1) as x, a1 from qry_0
> where the projected scalar subquery cannot be pushed down, but the rest of the query can will result in the with plan for qry_1 not being associated with the parent RelationalPlan and results in an exception that the temporary table cannot be found. This does not occur if the clause is inlined (9.0+).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months