April 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2459) WITH statement translated wrongly for Oracle 10

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2459?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2459. ----------------------------------- Fix Version/s: 8.4 Resolution: Done Removed the use of the as column definition, which oracle does not support. > WITH statement translated wrongly for Oracle 10 > ------------------------------------------------ > > Key: TEIID-2459 > URL: https://issues.jboss.org/browse/TEIID-2459 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.7.6 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Fix For: 8.4 > > > I am using Oracle 10g [1] and I have set the Oracle version to 9.2 in a dynamic VDB [2]. > I am running simple WITH statement against Oracle: WITH x AS (select DATEVALUE from SMALLA) select DATEVALUE from x. Which throws [3]. Probably because Oracle 10 doesn't support column aliasing "WITH x (DATEVALUE)". > [1] Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production > With the Partitioning, OLAP and Data Mining options > [2] <property name="DatabaseVersion" value="9.2" /> > [3] Caused by: org.teiid.translator.TranslatorException: Error Code:32033 Message:Remote org.teiid.translator.jdbc.JDBCExecutionException: Error Code:32033 Message:'ORA-32033: unsupported column aliasing > ' error executing statement(s): [Prepared Values: [] SQL: WITH x (DATEVALUE) AS (SELECT g_0."DATEVALUE" FROM "BQT2_RO"."SMALLA" g_0) SELECT g_0.DATEVALUE FROM x g_0] -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2432. --------------------------------- Labels: Alpha2 (was: ) Resolution: Done Added the above mentioned metadata load states to Model. > Dynamic VDB isLoading state doesnt change on fail > ------------------------------------------------- > > Key: TEIID-2432 > URL: https://issues.jboss.org/browse/TEIID-2432 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.4 > > > I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB deployment is finished. > In my case the VDB dataSource is not available. I can see in the server log that the deployment fails immediately, but the isLoading state remains true. > Is this in error, or what status should we be checking? -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2432) Dynamic VDB isLoading state doesnt change on fail

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2432: -------------------------------- Issue Type: Enhancement (was: Feature Request) Git Pull Request: https://github.com/rareddy/teiid/pull/new/TEIID-2432 Complexity: Low > Dynamic VDB isLoading state doesnt change on fail > ------------------------------------------------- > > Key: TEIID-2432 > URL: https://issues.jboss.org/browse/TEIID-2432 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.4 > > > I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB deployment is finished. > In my case the VDB dataSource is not available. I can see in the server log that the deployment fails immediately, but the isLoading state remains true. > Is this in error, or what status should we be checking? -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2459) WITH statement translated wrongly for Oracle 10

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2459?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-2459: -------------------------------- Affects Version/s: 7.7.4 > WITH statement translated wrongly for Oracle 10 > ------------------------------------------------ > > Key: TEIID-2459 > URL: https://issues.jboss.org/browse/TEIID-2459 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.7.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > I am using Oracle 10g [1] and I have set the Oracle version to 9.2 in a dynamic VDB [2]. > I am running simple WITH statement against Oracle: WITH x AS (select DATEVALUE from SMALLA) select DATEVALUE from x. Which throws [3]. Probably because Oracle 10 doesn't support column aliasing "WITH x (DATEVALUE)". > [1] Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production > With the Partitioning, OLAP and Data Mining options > [2] <property name="DatabaseVersion" value="9.2" /> > [3] Caused by: org.teiid.translator.TranslatorException: Error Code:32033 Message:Remote org.teiid.translator.jdbc.JDBCExecutionException: Error Code:32033 Message:'ORA-32033: unsupported column aliasing > ' error executing statement(s): [Prepared Values: [] SQL: WITH x (DATEVALUE) AS (SELECT g_0."DATEVALUE" FROM "BQT2_RO"."SMALLA" g_0) SELECT g_0.DATEVALUE FROM x g_0] -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2459) WITH statement translated wrongly for Oracle 10

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2459?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-2459: -------------------------------- Affects Version/s: 7.7.6 (was: 7.7.4) > WITH statement translated wrongly for Oracle 10 > ------------------------------------------------ > > Key: TEIID-2459 > URL: https://issues.jboss.org/browse/TEIID-2459 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.7.6 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > I am using Oracle 10g [1] and I have set the Oracle version to 9.2 in a dynamic VDB [2]. > I am running simple WITH statement against Oracle: WITH x AS (select DATEVALUE from SMALLA) select DATEVALUE from x. Which throws [3]. Probably because Oracle 10 doesn't support column aliasing "WITH x (DATEVALUE)". > [1] Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production > With the Partitioning, OLAP and Data Mining options > [2] <property name="DatabaseVersion" value="9.2" /> > [3] Caused by: org.teiid.translator.TranslatorException: Error Code:32033 Message:Remote org.teiid.translator.jdbc.JDBCExecutionException: Error Code:32033 Message:'ORA-32033: unsupported column aliasing > ' error executing statement(s): [Prepared Values: [] SQL: WITH x (DATEVALUE) AS (SELECT g_0."DATEVALUE" FROM "BQT2_RO"."SMALLA" g_0) SELECT g_0.DATEVALUE FROM x g_0] -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2459) WITH statement translated wrongly for Oracle 10

by Filip Nguyen (JIRA)

Filip Nguyen created TEIID-2459: ----------------------------------- Summary: WITH statement translated wrongly for Oracle 10 Key: TEIID-2459 URL: https://issues.jboss.org/browse/TEIID-2459 Project: Teiid Issue Type: Bug Reporter: Filip Nguyen Assignee: Steven Hawkins I am using Oracle 10g [1] and I have set the Oracle version to 9.2 in a dynamic VDB [2]. I am running simple WITH statement against Oracle: WITH x AS (select DATEVALUE from SMALLA) select DATEVALUE from x. Which throws [3]. Probably because Oracle 10 doesn't support column aliasing "WITH x (DATEVALUE)". [1] Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production With the Partitioning, OLAP and Data Mining options [2] <property name="DatabaseVersion" value="9.2" /> [3] Caused by: org.teiid.translator.TranslatorException: Error Code:32033 Message:Remote org.teiid.translator.jdbc.JDBCExecutionException: Error Code:32033 Message:'ORA-32033: unsupported column aliasing ' error executing statement(s): [Prepared Values: [] SQL: WITH x (DATEVALUE) AS (SELECT g_0."DATEVALUE" FROM "BQT2_RO"."SMALLA" g_0) SELECT g_0.DATEVALUE FROM x g_0] -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2458. ----------------------------------- Resolution: Deferred Unless the user is comfortable with disabling all subquery support there may be instances where Sybase subquery support has issues. > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2458: ---------------------------------- Workaround Description: Use an custom translator to set supportsOnlyCorrelatedSubqueries to true, which will disable a non-correlated subquery pushdown such as this. However similar issues may still exist with other subqueries. Workaround: Workaround Exists > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2458: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=912548 > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2458: ------------------------------------ >From a conversation between Warren and Steve, Steve's conclusion: This is a third-party issue in an uncommon case so I would not likely do much with it other than list possible workarounds on the JIRA if one is created. Since this is a uncommon use case, this jira is only being submitted for historical purposes and to document any possible workarounds that might be known. > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2013