January 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3776) Teiid throws NPE if query contains AVG function on varchar type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3776?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3776. --------------------------------- > Teiid throws NPE if query contains AVG function on varchar type > --------------------------------------------------------------- > > Key: TEIID-3776 > URL: https://issues.jboss.org/browse/TEIID-3776 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Execution of this query ends with NPE in Teiid: > SELECT stringnum FROM bqt1.smalla GROUP BY stringnum HAVING avg(stringnum) = '1' > Expected result: > Exception similar to - org.teiid.api.exception.query.QueryValidatorException: TEIID30492 The aggregate function AVG cannot be used with non-numeric expressions: AVG(BQT1.SmallA.StringNum) > Actual result: > {code:text} > 12:27:32,829 DEBUG [org.teiid.TRANSPORT] (New I/O worker #7) processing message:MessageHolder: key=619 contents=Invoke interface org.teiid.client.DQP.executeRequest > 12:27:32,830 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) Request Thread r77C2X0C5Gwa.10 with state NEW > 12:27:32,830 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) r77C2X0C5Gwa.10 Non-cachable command. > 12:27:32,830 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) r77C2X0C5Gwa.10 executing SELECT stringnum FROM bqt1.smalla GROUP BY stringnum HAVING avg(stringnum) = '1' > 12:27:32,831 ERROR [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) TEIID30019 Unexpected exception for request r77C2X0C5Gwa.10: java.lang.NullPointerException > at org.teiid.query.resolver.util.ResolverVisitor.resolveCompareCriteria(ResolverVisitor.java:767) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:248) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.lang.CompareCriteria.acceptVisitor(CompareCriteria.java:126) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:54) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:61) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.postVisitVisitor(SimpleQueryResolver.java:197) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:135) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.lang.CompareCriteria.acceptVisitor(CompareCriteria.java:126) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:214) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:69) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:271) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:124) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:260) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:369) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.Request.processRequest(Request.java:435) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:613) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:315) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40] > 12:27:32,832 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) java.lang.NullPointerException Sending error to client r77C2X0C5Gwa.10 > 12:27:32,833 DEBUG [org.teiid.TRANSPORT] (Worker52_QueryProcessorQueue378) send message: MessageHolder: key=619 contents=ResultsMessage rowCount=0 finalRow=-1 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3815) Oracle translator - OFFSET function does not work

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3815?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3815. --------------------------------- > Oracle translator - OFFSET function does not work > ------------------------------------------------- > > Key: TEIID-3815 > URL: https://issues.jboss.org/browse/TEIID-3815 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.2.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.2, 8.13 > > > Oracle translator translates OFFSET function as: > {code:sql} > SELECT c_0 FROM (SELECT VIEW_FOR_LIMIT.*, ROWNUM ROWNUM_ FROM (***Query***) VIEW_FOR_LIMIT WHERE ROWNUM <= -2147483604) WHERE ROWNUM_ > 45 > {code} > This always returns an empty result because of *ROWNUM <= -2147483604*. > Example: > Query: > {code:sql} > SELECT INTKEY FROM bqt1.smalla ORDER BY INTKEY OFFSET 45 ROWS > {code} > Source-specific command: > {code:sql} > SELECT c_0 FROM (SELECT VIEW_FOR_LIMIT.*, ROWNUM ROWNUM_ FROM (SELECT trunc(g_0."INTKEY") AS c_0 FROM "DV"."SMALLA" g_0 ORDER BY c_0) VIEW_FOR_LIMIT WHERE ROWNUM <= -2147483604) WHERE ROWNUM_ > 45 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3686) OData DELETE nonexisting row - wrong response code

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3686?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3686. --------------------------------- > OData DELETE nonexisting row - wrong response code > -------------------------------------------------- > > Key: TEIID-3686 > URL: https://issues.jboss.org/browse/TEIID-3686 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.12, 8.7.2.6_2 > > > I deployed VDB that can be accessed with OData. When I perform DELETE request to remove row for first time response code is 200 OK (maybe it should be 204) but when I repeat the same DELETE request and tried to delete already deleted entry, response is again 200 OK, but it should be 404 Not Found. Same thing happens even I when tried to delete entry with id that doesn't exist at all. > Only indication of this problem is in the server log: > {code:plain}INFO [org.teiid.ODATA] (http-/127.0.0.1:8080-1) no entity to delete in = BooksMySQL.BOOKS with key= ('1') > {code} > I think that response code for deleting row that doesn't exist should be different than 200 OK. > For example the service at odata.org returns following content with response code 404 Not Found: > {code:xml} > <?xml version="1.0" encoding="utf-8" standalone="yes"?> > <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> > <code></code> > <message xml:lang="en-US">Resource not found for the segment 'Products'.</message> > </error> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3811) Teiid Embedded with remote JDBC susceptible to exploit with common-collections in classpath

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3811?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3811. --------------------------------- > Teiid Embedded with remote JDBC susceptible to exploit with common-collections in classpath > ------------------------------------------------------------------------------------------- > > Key: TEIID-3811 > URL: https://issues.jboss.org/browse/TEIID-3811 > Project: Teiid > Issue Type: Quality Risk > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12.2, 8.13 > > > This issue is to add at least a documentation note warning against - http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-j... > While remote JDBC is not enabled by default and common-collections is not in the classpath it is possible that common-collections could be picked up from the environment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3787) ignored properties in dynamic vdb should be flagged with a WARN log entry

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3787?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3787. --------------------------------- > ignored properties in dynamic vdb should be flagged with a WARN log entry > ------------------------------------------------------------------------- > > Key: TEIID-3787 > URL: https://issues.jboss.org/browse/TEIID-3787 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.1.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.12.2, 8.13 > > > Invalid properties are silently ignored, this can be troublesome to diagnose when there is a case mismatch, etc. useConnectorMetadata vs. UseConnectorMetadata > {code:java} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="test" version="1"> > <property name="useConnectorMetadata" value="true"/> > <property name="BREAK ME" value="true"/> > > <model name="EMPTY"> > > </model> > </vdb> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3582) Add the query requestID to all lines for that query in the logs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3582?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3582. --------------------------------- > Add the query requestID to all lines for that query in the logs > --------------------------------------------------------------- > > Key: TEIID-3582 > URL: https://issues.jboss.org/browse/TEIID-3582 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Fix For: 8.12.2, 8.13 > > > Currently when running a query, the logs show the requestId on most of the lines but not all, especially CONNECTOR. > for example, the following line doesn't have it: > 14:13:34,071 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue13) Source-specific command: .... > That's the problem. When lots of queries are running, user wants to grep through the log for that requestid and get just that one query's stuff. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3771) Teiid throws an NPE while executing query with nested subquery IN predicate

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3771?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3771. --------------------------------- > Teiid throws an NPE while executing query with nested subquery IN predicate > --------------------------------------------------------------------------- > > Key: TEIID-3771 > URL: https://issues.jboss.org/browse/TEIID-3771 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Teiid throws an NPE while executing query with double IN predicate. Example query: > SELECT intkey FROM BQT1.SmallA AS A WHERE INTKEY IN (SELECT CONVERT(STRINGKEY, INTEGER) FROM BQT1.SMALLA AS A WHERE STRINGKEY IN (SELECT CONVERT(INTKEY, STRING) FROM BQT1.SMALLA AS B WHERE A.INTNUM = B.INTNUM)) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3481) Wrong syntax of cache hints in the documentation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3481?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3481. --------------------------------- > Wrong syntax of cache hints in the documentation > ------------------------------------------------- > > Key: TEIID-3481 > URL: https://issues.jboss.org/browse/TEIID-3481 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 8.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The syntax for cache hint is as follows: > (1) cache[([pref_mem] [ttl:n] [updatable])] [scope:(session|user|vdb)] > So if user wants to use cache for specific scope (e.g. session) according to declared syntax it should be: > (2) cache scope:session > But using (2) teiid ignores the scope. What teiid accepts is: > cache(scope:session) > So I suggest to update (1) to: > cache[([pref_mem] [ttl:n] [updatable] [scope:(session|user|vdb)]*)]* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3767) HBase - Phoenix does not support LIKE ESCAPE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3767?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3767. --------------------------------- > HBase - Phoenix does not support LIKE ESCAPE > -------------------------------------------- > > Key: TEIID-3767 > URL: https://issues.jboss.org/browse/TEIID-3767 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Phoenix does not support LIKE ESCAPE. There is hardcoded escape character \. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3527) Missing ODBC port number in the log during shutdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3527?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3527. --------------------------------- > Missing ODBC port number in the log during shutdown > --------------------------------------------------- > > Key: TEIID-3527 > URL: https://issues.jboss.org/browse/TEIID-3527 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.11 > > > There is missing ODBC port number in the log during shutdown: > INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50039 Teiid JDBC - Name = jdbc, Host = localhost, Port = 31000 has been shutdown. > INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID50040 Teiid ODBC - Name = localhost, Host = 35432, Port = {2} has been shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016