[JBoss JIRA] (TEIID-3785) PostgreSQL - Large Objects may not be used in auto-commit mode.
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3785?page=com.atlassian.jira.plugin... ]
Tom Arnold updated TEIID-3785:
------------------------------
Description:
Using Teiid 8.11.3 with PostgreSQL 9.1 and PostGIS. Doing a simple query with a spatial filter causes this stacktrace in the log, and 0 results to be returned (probably because I have partialResultsMode enabled).
{code}
select item_id from items where st_interesects(footprint, st_geomfromtext('point(0 0)',4326));
{code}
{code}
16:42:10,222 WARN [org.teiid.CONNECTOR] (Worker19_QueryProcessorQueue487) 8I60feXXYm5f Connector worker process failed for atomic-request=8I60feXXYm5f.166.0.82: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['javax.sql.rowset.serial.SerialBlob@4fe24349'] SQL: SELECT g_0."item_id" AS c_0 FROM "foo"."items" AS g_0 WHERE st_intersects(g_0."footprint", st_geomfromwkb(?, 4326)) = TRUE]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:341)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source) [:1.7.0_85]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_85]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_85]
at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
at com.sun.proxy.$Proxy87.execute(Unknown Source)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107)
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_85]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58)
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) [rt.jar:1.7.0_85]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_85]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_85]
Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode.
at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:301)
at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:288)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setBlob(AbstractJdbc2Statement.java:3051)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1832)
at org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement.java:1481)
at org.postgresql.jdbc3g.AbstractJdbc3gStatement.setObject(AbstractJdbc3gStatement.java:46)
at org.postgresql.jdbc4.AbstractJdbc4Statement.setObject(AbstractJdbc4Statement.java:70)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1864)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:957)
at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:936) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.translator.jdbc.JDBCBaseExecution.bind(JDBCBaseExecution.java:107) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:122) [translator-jdbc-8.11.3.jar:8.11.3]
... 17 more
{code}
It looks like the issue is binding the WKB blob. Overriding the PostgreSQL translator and setting {{useStreamsForLobs()}} to {{true}} seems to fix the issue.
was:
Using Teiid 8.11.3 with PostgreSQL 9.1 and PostGIS. Doing a simple query with a spatial filter causes this stacktrace in the log, and 0 results to be returned (probably because I have partialResultsMode enabled).
{code}
select item_id from items where st_interesects(footprint, st_geomfromtext('point(0 0)',4326));
{code}
{code}
16:42:10,222 WARN [org.teiid.CONNECTOR] (Worker19_QueryProcessorQueue487) 8I60feXXYm5f Connector worker process failed for atomic-request=8I60feXXYm5f.166.0.82: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['javax.sql.rowset.serial.SerialBlob@4fe24349'] SQL: SELECT g_0."item_id" AS c_0 FROM "foo"."items" AS g_0 WHERE st_intersects(g_0."footprint", st_geomfromwkb(?, 4326)) = TRUE LIMIT 3001]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:341)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source) [:1.7.0_85]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_85]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_85]
at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
at com.sun.proxy.$Proxy87.execute(Unknown Source)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107)
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_85]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58)
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) [rt.jar:1.7.0_85]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_85]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_85]
Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode.
at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:301)
at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:288)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setBlob(AbstractJdbc2Statement.java:3051)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1832)
at org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement.java:1481)
at org.postgresql.jdbc3g.AbstractJdbc3gStatement.setObject(AbstractJdbc3gStatement.java:46)
at org.postgresql.jdbc4.AbstractJdbc4Statement.setObject(AbstractJdbc4Statement.java:70)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1864)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:957)
at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:936) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.translator.jdbc.JDBCBaseExecution.bind(JDBCBaseExecution.java:107) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:122) [translator-jdbc-8.11.3.jar:8.11.3]
... 17 more
{code}
It looks like the issue is binding the WKB blob. Overriding the PostgreSQL translator and setting {{useStreamsForLobs()}} to {{true}} seems to fix the issue.
> PostgreSQL - Large Objects may not be used in auto-commit mode.
> ---------------------------------------------------------------
>
> Key: TEIID-3785
> URL: https://issues.jboss.org/browse/TEIID-3785
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.11.3
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
>
> Using Teiid 8.11.3 with PostgreSQL 9.1 and PostGIS. Doing a simple query with a spatial filter causes this stacktrace in the log, and 0 results to be returned (probably because I have partialResultsMode enabled).
> {code}
> select item_id from items where st_interesects(footprint, st_geomfromtext('point(0 0)',4326));
> {code}
> {code}
> 16:42:10,222 WARN [org.teiid.CONNECTOR] (Worker19_QueryProcessorQueue487) 8I60feXXYm5f Connector worker process failed for atomic-request=8I60feXXYm5f.166.0.82: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['javax.sql.rowset.serial.SerialBlob@4fe24349'] SQL: SELECT g_0."item_id" AS c_0 FROM "foo"."items" AS g_0 WHERE st_intersects(g_0."footprint", st_geomfromwkb(?, 4326)) = TRUE]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.11.3.jar:8.11.3]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:341)
> at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source) [:1.7.0_85]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_85]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_85]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy87.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_85]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58)
> 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) [rt.jar:1.7.0_85]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_85]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_85]
> Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode.
> at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:301)
> at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:288)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.setBlob(AbstractJdbc2Statement.java:3051)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1832)
> at org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement.java:1481)
> at org.postgresql.jdbc3g.AbstractJdbc3gStatement.setObject(AbstractJdbc3gStatement.java:46)
> at org.postgresql.jdbc4.AbstractJdbc4Statement.setObject(AbstractJdbc4Statement.java:70)
> at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1864)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:957)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:936) [translator-jdbc-8.11.3.jar:8.11.3]
> at org.teiid.translator.jdbc.JDBCBaseExecution.bind(JDBCBaseExecution.java:107) [translator-jdbc-8.11.3.jar:8.11.3]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:122) [translator-jdbc-8.11.3.jar:8.11.3]
> ... 17 more
> {code}
> It looks like the issue is binding the WKB blob. Overriding the PostgreSQL translator and setting {{useStreamsForLobs()}} to {{true}} seems to fix the issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3785) PostgreSQL - Large Objects may not be used in auto-commit mode.
by Tom Arnold (JIRA)
Tom Arnold created TEIID-3785:
---------------------------------
Summary: PostgreSQL - Large Objects may not be used in auto-commit mode.
Key: TEIID-3785
URL: https://issues.jboss.org/browse/TEIID-3785
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 8.11.3
Reporter: Tom Arnold
Assignee: Steven Hawkins
Using Teiid 8.11.3 with PostgreSQL 9.1 and PostGIS. Doing a simple query with a spatial filter causes this stacktrace in the log and 0 results to be returned.
{code}
select item_id from items where st_interesects(footprint, st_geomfromtext('point(0 0)',4326));
{code}
{code}
16:42:10,222 WARN [org.teiid.CONNECTOR] (Worker19_QueryProcessorQueue487) 8I60feXXYm5f Connector worker process failed for atomic-request=8I60feXXYm5f.166.0.82: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['javax.sql.rowset.serial.SerialBlob@4fe24349'] SQL: SELECT g_0."item_id" AS c_0 FROM "foo"."items" AS g_0 WHERE st_intersects(g_0."footprint", st_geomfromwkb(?, 4326)) = TRUE LIMIT 3001]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:341)
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source) [:1.7.0_85]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_85]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_85]
at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
at com.sun.proxy.$Proxy87.execute(Unknown Source)
at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110)
at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107)
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_85]
at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58)
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) [rt.jar:1.7.0_85]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_85]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_85]
Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode.
at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:301)
at org.postgresql.largeobject.LargeObjectManager.createLO(LargeObjectManager.java:288)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setBlob(AbstractJdbc2Statement.java:3051)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1832)
at org.postgresql.jdbc3.AbstractJdbc3Statement.setObject(AbstractJdbc3Statement.java:1481)
at org.postgresql.jdbc3g.AbstractJdbc3gStatement.setObject(AbstractJdbc3gStatement.java:46)
at org.postgresql.jdbc4.AbstractJdbc4Statement.setObject(AbstractJdbc4Statement.java:70)
at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1864)
at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:957)
at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:936) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.translator.jdbc.JDBCBaseExecution.bind(JDBCBaseExecution.java:107) [translator-jdbc-8.11.3.jar:8.11.3]
at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:122) [translator-jdbc-8.11.3.jar:8.11.3]
... 17 more
{code}
It looks like the issue is binding the WKB blob. Overriding the PostgreSQL translator and setting {{useStreamsForLobs()}} to {{true}} seems to fix the issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3361) Add source query details to the command log
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3361?page=com.atlassian.jira.plugin... ]
Work on TEIID-3361 started by Steven Hawkins.
---------------------------------------------
> Add source query details to the command log
> -------------------------------------------
>
> Key: TEIID-3361
> URL: https://issues.jboss.org/browse/TEIID-3361
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12.1
>
>
> The command log for convenience only contains the Teiid sql form of the source query. It would be good to have the translators also add their actual form of the source query when possible to the command log just to have a single place to track things down.
> Currently this info is logged to the CONNECTOR context inconsistently in each translator.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3682) Add logon properties to audit messages
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3682?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3682:
----------------------------------
Fix Version/s: 8.12.x
> Add logon properties to audit messages
> --------------------------------------
>
> Key: TEIID-3682
> URL: https://issues.jboss.org/browse/TEIID-3682
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12.x
>
>
> We expanded logon information in 8.12, but did not yet include all logon properties, which can include the client ip address - but there are limitations since the client ip and related fields would only be set for JDBC connections and not yet for local usage through ODBC/web.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3780) Hive: Convert "UseDatabaseMetaData: to be an translator import property
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3780?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3780.
-----------------------------------
Fix Version/s: 8.13
Resolution: Done
Merged the logic into the importer. Left the translator property for now for backwards compatibility. The docs already referred to this as an importer property, so no change was needed there.
> Hive: Convert "UseDatabaseMetaData: to be an translator import property
> -----------------------------------------------------------------------
>
> Key: TEIID-3780
> URL: https://issues.jboss.org/browse/TEIID-3780
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Affects Versions: 8.11
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.12.1, 8.13
>
>
> Currently "UseDatabaseMetadata" as been designed as Translator property, may be this should be designed as translator importer property?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3669) Look at consolidating to a single session service
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3669?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3669:
---------------------------------------
With the changes in place, the last comment is an issue. We are effectively assuming in some tests that the embedded transport is wide open - but with a security domain set, we'll get an exception. We may need to add a notion of trust all for non-odbc local access.
> Look at consolidating to a single session service
> -------------------------------------------------
>
> Key: TEIID-3669
> URL: https://issues.jboss.org/browse/TEIID-3669
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0
>
>
> We should consider moving back to a single session service in Teiid 9 as most of the constraints will be specified on a vdb basis (such as security domain, auth type, etc.) and the separation in the session service causes issues with sessions originating in different transports - TEIID-3663
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3783) Error when limit/sort is pushed above a window function
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3783?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3783.
-----------------------------------
Resolution: Done
Resolved by preserving aliases in the sorting until it's pushed below the projection.
> Error when limit/sort is pushed above a window function
> -------------------------------------------------------
>
> Key: TEIID-3783
> URL: https://issues.jboss.org/browse/TEIID-3783
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.12.1, 8.13
>
>
> TEIID-3568 introduced a regression by pushing a sort over a project node, but not accounting for aliases. This can be reproduced with a query such as:
> select column_a, column_b from (select sum(column_a) over (partition by key_column) as column_a, key_column from a ) a left outer join ( select sum(column_b) over (partition by key_column) as column_b, key_column from b) b on a.key_column = b.key_column order by column_a desc limit 10
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3783) Error when limit/sort is pushed above a window function
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3783:
-------------------------------------
Summary: Error when limit/sort is pushed above a window function
Key: TEIID-3783
URL: https://issues.jboss.org/browse/TEIID-3783
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.12
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12.1, 8.13
TEIID-3568 introduced a regression by pushing a sort over a project node, but not accounting for aliases. This can be reproduced with a query such as:
select column_a, column_b from (select sum(column_a) over (partition by key_column) as column_a, key_column from a ) a left outer join ( select sum(column_b) over (partition by key_column) as column_b, key_column from b) b on a.key_column = b.key_column order by column_a desc limit 10
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months