[JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2730.
-----------------------------------
Fix Version/s: 8.6
Resolution: Done
Thanks Ben. I just refined what you added.
Marking as resolved again. The docs now note (similar to ansi mode with MySQL) that we expect quoting to be turned on with sybase/jconnect.
> Cannot query Sybase database with jconn3.jar
> --------------------------------------------
>
> Key: TEIID-2730
> URL: https://issues.jboss.org/browse/TEIID-2730
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.4
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Fix For: 8.6
>
> Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar
>
>
> In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar.
> I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> Console:
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0
> ============================================================================
> 10:55:07,362 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31 1:05:35 2009;IsolationLevel=2
> 10:55:07,555 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'.
> at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> 10:55:07,568 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'.
> ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (TEIID-2715) Created and registered MXD, extra metadata is not visible when queried.
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2715:
----------------------------------
Issue Type: Enhancement (was: Bug)
Workaround Description: Create a view that contains the desired properties by joining against the properties table.
Workaround: Workaround Exists
Switching to an enhancement as given the current structure of the system schema there isn't an inherent issue now that TEIID-2718 has been resolved.
The general question here is about the usability of extension metadata from odata. There isn't currently a good relationship between the properties table and all of the object type tables.
The workaround is to have the user create a view to denormalize the properties how ever they see fit.
As for built-in work, to expose the extension properties a little more naturally we could add columns to the properties table so that it can be queried by something other than uid, or add navigatable relations like table_properties. There may also be something in odata's metadata that will allow arbitrary properties - although I did not see that at first glance.
> Created and registered MXD, extra metadata is not visible when queried.
> -----------------------------------------------------------------------
>
> Key: TEIID-2715
> URL: https://issues.jboss.org/browse/TEIID-2715
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 8.6
> Environment: Windows 7
> Reporter: Alex Khvatov
> Assignee: Steven Hawkins
>
> x`Hi,
> I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata:
> http://localhost:8080/odata/MCR_VDB/Tables?$format=json
> http://localhost:8080/odata/MCR_VDB/Columns?$format=json
> Both documents returned did not contain any extra metadata I defined.
> HELP!
> Thanks.
> Alex
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2730:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1028380|https://bugzilla.redhat.com/show_bug.cgi?id=1028380] from NEW to ASSIGNED
> Cannot query Sybase database with jconn3.jar
> --------------------------------------------
>
> Key: TEIID-2730
> URL: https://issues.jboss.org/browse/TEIID-2730
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.4
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar
>
>
> In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar.
> I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> Console:
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0
> ============================================================================
> 10:55:07,362 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31 1:05:35 2009;IsolationLevel=2
> 10:55:07,555 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'.
> at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> 10:55:07,568 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'.
> ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (TEIID-2730) Cannot query Sybase database with jconn3.jar
by B Long (JIRA)
[ https://issues.jboss.org/browse/TEIID-2730?page=com.atlassian.jira.plugin... ]
B Long commented on TEIID-2730:
-------------------------------
Added to documentation: https://docs.jboss.org/author/display/TEIID/JDBC+Translator
> Cannot query Sybase database with jconn3.jar
> --------------------------------------------
>
> Key: TEIID-2730
> URL: https://issues.jboss.org/browse/TEIID-2730
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.4
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Attachments: bqtHNB.vdb, bqt_HNB.xmi, jconn3.jar
>
>
> In teiid designer, I created a connection profile to Sybase database with URL jdbc:sybase:Tds:vmg07.mw.lab.eng.bos.redhat.com:5000/bqt2 and driver jconn3.jar.
> I created a relational source model from the jdbc connection and VDB with the source model. Then I deployed the VDB and executed query select * from "bqt_HNB"."g1" which resulted in this error message:
> TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> Console:
> OPTIMIZATION COMPLETE:
> PROCESSOR PLAN:
> AccessNode(0) output=[bqt_HNB.g1.e1, bqt_HNB.g1.e2] SELECT g_0.e1, g_0.e2 FROM bqt_HNB.g1 AS g_0
> ============================================================================
> 10:55:07,362 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) SybaseExecutionFactory Commit=true;DatabaseProductName=Adaptive Server Enterprise;DatabaseProductVersion=Adaptive Server Enterprise/15.0.3/EBF 16549 ESD#1/P/x86_64/Enterprise Linux/ase1503/2681/64-bit/FBO/Mon Mar 9 04:10:47 2009;DriverMajorVersion=6;DriverMajorVersion=0;DriverName=jConnect (TM) for JDBC (TM);DriverVersion=jConnect (TM) for JDBC(TM)/6.05(Build 26564)/P/EBF16903/JDK14/Sun May 31 1:05:35 2009;IsolationLevel=2
> 10:55:07,555 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) Connector worker process failed for atomic-request=dg2FpIhALlUI.0.0.0: org.teiid.translator.jdbc.JDBCExecutionException: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:444) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:157) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:154) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_45]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_45]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-2.jar:8.4.1-redhat-2]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
> Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near 'e1'.
> at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
> at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:84)
> ... 13 more
> 10:55:07,568 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30020 Processing exception for request dg2FpIhALlUI.0 'TEIID30504 bqt_HNB: 102 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."e1", g_0."e2" FROM "bqt2"."dbo"."g1" g_0]'. Originally TeiidProcessingException 'Incorrect syntax near 'e1'.
> ' com.sybase.jdbc3.tds.Tds.a(Unknown Source). Enable more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (TEIID-2745) Evaluatable subquery in ON clause produces invalid query
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2745?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2745:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1032794
> Evaluatable subquery in ON clause produces invalid query
> --------------------------------------------------------
>
> Key: TEIID-2745
> URL: https://issues.jboss.org/browse/TEIID-2745
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> Using an evaluatable subquery, such as a scalar subquery in an outer join on clause will result in all criteria being removed and an invalid source query being issued.
> For example:
> with a (x, y, z) as (select e1, e2, e3 from pm1.g1 limit 1) SELECT pm2.g1.e1 from pm2.g1 left outer join pm2.g2 on (pm2.g1.e2 = pm2.g2.e2 and pm2.g1.e1 = (select a.x from a))
> And a source that doesn't support with (or the with clause cannot be pushed as part of the main query), then the evaluation of the scalar subquery will block and cause the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months
[JBoss JIRA] (TEIID-2748) Ensure pushdown of multisource column expressions
by Mark Addleman (JIRA)
Mark Addleman created TEIID-2748:
------------------------------------
Summary: Ensure pushdown of multisource column expressions
Key: TEIID-2748
URL: https://issues.jboss.org/browse/TEIID-2748
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Mark Addleman
Assignee: Steven Hawkins
> The issue is that the criteria is not making it into the proper position for the multisource logic to have an effect. It is implicit that multisource required a translator that supported equality comparison at least. In this case adding the xpathValue function, because of weaknesses with the detection of a fully evaluatable, is then inhibiting the proper placement. That last one is easy to fix and I can ensure that more complex cases are covered as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 5 months