April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2864) With select fails on Teiid 8.7-beta1 on MS SQL Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2864?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2864. --------------------------------- > With select fails on Teiid 8.7-beta1 on MS SQL Server > ----------------------------------------------------- > > Key: TEIID-2864 > URL: https://issues.jboss.org/browse/TEIID-2864 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.4 > Reporter: Alex K. > Assignee: Steven Hawkins > Fix For: 8.7 > > > following query fails for me on Teiid 8.7-beta1 on MS SQL Server in queries containing WITH, UNION ALL and LIMIT clauses (The exception is being thrown only when having LIMIT clause, without the LIMIT it seems working) > {code:sql} > WITH qry_0 as > (SELECT t1.f a FROM test_tables_ms.test_e AS t1 GROUP BY t1.f) > SELECT a as a1 from qry_0 > union all > SELECT a from qry_0 > LIMIT 10 > {code} > Exception: > {code:java} > WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue30) beKbgt/pu4f4 Connector worker process failed for atomic-request=beKbgt/pu4f4.11.2.6: org.teiid.translator.jdbc.JDBCExecutionException: 156 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT TOP 10 * FROM (WITH qry_0 (a) AS (SELECT g_0."f" FROM "test_tables"."dbo"."test_e" g_0 GROUP BY g_0."f") SELECT g_1.a AS c_0 FROM qry_0 g_1 UNION ALL SELECT g_0.a AS c_0 FROM qry_0 g_0) AS X] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:317) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.7.0.Beta1.jar:8.7.0.Beta1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'WITH'. > at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350) > at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696) > at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180) > at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155) > at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) > ... 13 more > 19:23:44,606 WARN [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue31) beKbgt/pu4f4 TEIID30020 Processing exception for request beKbgt/pu4f4.11 'TEIID30504 test_tables_ms: 156 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT TOP 10 * FROM (WITH qry_0 (a) AS (SELECT g_0."f" FROM "test_tables"."dbo"."test_e" g_0 GROUP BY g_0."f") SELECT g_1.a AS c_0 FROM qry_0 g_1 UNION ALL SELECT g_0.a AS c_0 FROM qry_0 g_0) AS X]'. Originally TeiidProcessingException 'Incorrect syntax near the keyword 'WITH'.' SQLServerException.java:216. Enable more detailed logging to see the entire stacktrace. > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2664) Misc OData issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2664?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2664. --------------------------------- > Misc OData issues > ----------------- > > Key: TEIID-2664 > URL: https://issues.jboss.org/browse/TEIID-2664 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5, 8.7 > > > Make TeiidProviderProducer's client connection a bounded concurrent map where entries can be expired on given cached time. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2763) kerberosServicePrincipleName as user when dealing with kerberos security domain

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2763?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2763. --------------------------------- > kerberosServicePrincipleName as user when dealing with kerberos security domain > ------------------------------------------------------------------------------- > > Key: TEIID-2763 > URL: https://issues.jboss.org/browse/TEIID-2763 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.6 > Environment: Windows 2008R2 > Reporter: Andy Yip > Assignee: Ramesh Reddy > Labels: authentication, login-module > Fix For: 8.7 > > > When both the security-domain and krb5-domain is defined within the transport authentication element. The security-domain module does not take into account of kerberosServicePrincipleName. This means a username (and/or password) is still required in the connection url forthe security-domain's authentication/authorization. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2793) Searchablity check is too broad

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2793?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2793. --------------------------------- > Searchablity check is too broad > ------------------------------- > > Key: TEIID-2793 > URL: https://issues.jboss.org/browse/TEIID-2793 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > The check against searchabilty metadata gathers all column references in an expression, rather than checking just the expression itself. This was done probably to prevent comparisons such as convert(clob_col, string) = 'foo' - but this is inconsistent as we will happily push the same convert function in the select clause. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2780) Provide Translator for Apache SOLR

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2780?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2780. --------------------------------- > Provide Translator for Apache SOLR > ---------------------------------- > > Key: TEIID-2780 > URL: https://issues.jboss.org/browse/TEIID-2780 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha1, Alpha2 > Fix For: 8.7 > > > Create a translator for querying Apache SOLR > http://lucene.apache.org/solr/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2765) Add odata support for array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2765?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2765. --------------------------------- > Add odata support for array types > --------------------------------- > > Key: TEIID-2765 > URL: https://issues.jboss.org/browse/TEIID-2765 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > simple type arrays should be supported through odata with a mapping to a complex type. > It would be good to also support object type values also but that would seemingly be a large effort possibly involving custom odata4j serializers to define the complex type metadata and perform the serialization to a complex type value. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2843) MongoDB: ClassCastException while doing JOIN based query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2843?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2843. --------------------------------- > MongoDB: ClassCastException while doing JOIN based query > -------------------------------------------------------- > > Key: TEIID-2843 > URL: https://issues.jboss.org/browse/TEIID-2843 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3, mongodb > Fix For: 8.7 > > > With Schema like > {code} > CREATE FOREIGN TABLE Company ( > name varchar(50) PRIMARY KEY, > description varchar(256) > ) OPTIONS(UPDATABLE 'TRUE',"teiid_mongo:EMBEDDABLE" 'true'); > CREATE FOREIGN TABLE Job ( > jobId integer PRIMARY KEY, > description varchar(256), > companyname varchar(50), > FOREIGN KEY (companyname) REFERENCES Company (name) > ) OPTIONS(UPDATABLE 'TRUE', "teiid_mongo:EMBEDDABLE" 'true'); > > CREATE FOREIGN TABLE Employee ( > ename varchar(50) PRIMARY KEY, > jobId integer, > FOREIGN KEY (jobId) REFERENCES Job (jobId) > ) OPTIONS(UPDATABLE 'TRUE'); > {code} > then doing a single JOIN Query > {code} > select e.ename, c.name, j.description from Employee as e JOIN Job j ON e.jobId = j.jobId JOIN Company c ON j.companyname = c.name > {code} > fails with > {code} > 14:22:05,271 ERROR [org.teiid.PROCESSOR] (Worker23_QueryProcessorQueue432) 258Se2CWMytI TEIID30019 Unexpected exception for request 258Se2CWMytI.28: java.lang.ClassCastException: org.teiid.language.Join cannot be cast to org.teiid.language.NamedTable > at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:419) > at org.teiid.language.Join.acceptVisitor(Join.java:66) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT] > at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:95) > at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:106) > at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:482) > at org.teiid.language.Select.acceptVisitor(Select.java:103) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT] > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.7.0.Alpha3-SNAPSHOT.jar:8.7.0.Alpha3-SNAPSHOT] > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2859) Provide identity generation for TEXTTABLE and OBJECTTABLE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2859?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2859. --------------------------------- > Provide identity generation for TEXTTABLE and OBJECTTABLE > --------------------------------------------------------- > > Key: TEIID-2859 > URL: https://issues.jboss.org/browse/TEIID-2859 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.7 > > > Extend the functionality FOR ORDINALITY defined on XMLTABLE, to TEXTTABLE and OBJECTTABLE. > This will useful in providing a automatic identity key if the data is being read from sources where there is identity column provided. The faced the issue when loading a text file like > {code} > VA,F,1910,Mary,848 > VA,F,1911,Mary,747 > {code} > Where name each line is a separate row, but they do not have unique identifier attached with them. Also helpful with interfaces like OData where they require a PK on a table. This provides an easier alternative. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1896) incorrect xml generated from jsontoxml with nested arrays

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1896?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1896: ---------------------------------- Fix Version/s: 7.7.9 > incorrect xml generated from jsontoxml with nested arrays > --------------------------------------------------------- > > Key: TEIID-1896 > URL: https://issues.jboss.org/browse/TEIID-1896 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.0, 7.7.9 > > > Non-root arrays are being nested, which is against the expectation defined in the reference. Instead of: > <root> > <x> > <x>1</x> > <x>1</x> > </x> > </root> > it should be: > <root> > <x>1</x> > <x>1</x> > </root> -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2929: ----------------------------------- Summary: Provide ability define "execution properties" as VDB properties Key: TEIID-2929 URL: https://issues.jboss.org/browse/TEIID-2929 Project: Teiid Issue Type: Enhancement Components: Server Reporter: Ramesh Reddy Assignee: Steven Hawkins Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method. However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties. This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file. -- 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, 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 2014