November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1777) Ingres as source - 3 VQT Queries using COUNT(*) returning unexpected results

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1777?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1777. --------------------------------- > Ingres as source - 3 VQT Queries using COUNT(*) returning unexpected results > ---------------------------------------------------------------------------- > > Key: TEIID-1777 > URL: https://issues.jboss.org/browse/TEIID-1777 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > > EDS Query Testing is getting unexpected results on the following queries: > 3 queries involving COUNT(*) > > QUERY: SELECT COUNT(*) FROM VQT.Agg1 > COMMENT: Expected count of 47 rows but got count of 1. > Agg1 transformation: SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA GROUP BY BQT1.SmallA.StringNum > QUERY: SELECT COUNT(*) FROM VQT.Agg3 > COMMENT: Expected count of 1 but got count of 50. > Agg3 transformation: SELECT COUNT(*) FROM BQT1.SmallA > QUERY: SELECT COUNT(*) FROM VQT.Agg4 > COMMENT: Expected count of 47 but got count of 1. > Agg4 transformation: SELECT MIN(BQT1.SmallA.StringNum), SUM(BQT1.SmallA.IntKey), AVG(BQT1.SmallA.IntKey) FROM BQT1.SmallA GROUP BY BQT1.SmallA.StringNum -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1795) Long Running Queries Are Calculated Incorrectly

by Ted Jones (Created) (JIRA)

Long Running Queries Are Calculated Incorrectly ----------------------------------------------- Key: TEIID-1795 URL: https://issues.jboss.org/browse/TEIID-1795 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 7.5, 7.4 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 7.6 The long running query logic in DQPCore uses millisecs when comparing to the query threshhold which is in seconds. It should both be in seconds. // check if only need long running queries. long elapsedTime = System.currentTimeMillis() - req.getStartTime(); if (longRunningQueryThreshold == -1 || elapsedTime > longRunningQueryThreshold) { results.add(req); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
5
0 / 0

[JBoss JIRA] (TEIID-1789) Serial type failure

by Steven Hawkins (Created) (JIRA)

Serial type failure ------------------- Key: TEIID-1789 URL: https://issues.jboss.org/browse/TEIID-1789 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Teiid temp table serial types fail to auto-increment properly (causing an not-null constraint violation) if used on a table without a primary key. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-1621) Unexpected grouping for SELECT queries on views that include a GROUP BY

by Claudio Venturini (JIRA)

Unexpected grouping for SELECT queries on views that include a GROUP BY ----------------------------------------------------------------------- Key: TEIID-1621 URL: https://issues.jboss.org/browse/TEIID-1621 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Environment: Teiid 7.4 (with patch) deployed on JBoss AS 5.1, installed on Ubuntu Server 10.04 LTS. Four source models, two of which in MySQL 5.1.51 (on the same machine of JBoss), one on SQLServer 2000 (on another machine), and one on SQL Server 2005 (on another machine). All sources participate in XA transactions. Reporter: Claudio Venturini Assignee: Steven Hawkins Attachments: server.log I've a set of models like the one that I've already explained in https://issues.jboss.org/browse/TEIID-1562. In addition I've a physical model, named sole_rugiada_phy, which extracts data from a SQL Server 2005 database. On top of it there's a view model, named sole_rugiada_log, which transform some fields and does some joins grouping. In particular the base table named 'vendita_referenza' is defined as follows: {code:sql} SELECT SR_op.codop, CAST(SR_v.n_bolla AS VARCHAR) AS codice, SUP_ro.codref, SR_v.data, CAST(SR_v.n_prog AS INTEGER) AS n_prog, CAST(SUM(SR_v.quantita) AS INTEGER) AS quantita, SUM((((SUP_r.quantita / SUP_ro.quantita_reale) * SR_v.quantita) * SR_v.prezzo)) AS fatturato, COUNT(*) AS groupdim FROM ((sole_rugiada_phy.MISURA124.dbo.VENDITA_REFERENZA AS SR_v INNER JOIN support_log.mediator.referenza_op AS SUP_ro ON RTRIM(LTRIM(CAST(SR_v.codref AS VARCHAR))) = SUP_ro.codice) INNER JOIN support_log.mediator.referenza AS SUP_r ON SUP_ro.codref = SUP_r.codref) INNER JOIN sole_rugiada_log.misura124.solerugiada.op AS SR_op ON SUP_ro.codop = SR_op.codop WHERE SR_v.data >= PARSEDATE('20090701', 'yyyyMMdd') GROUP BY SR_op.codop, SR_v.data, SR_v.n_bolla, SR_v.n_prog, SUP_ro.codref {code} If I run the following query, that is a simple SELECT statement, everything works fine: {code:sql} SELECT codop, codice, codref, data, n_prog, quantita, fatturato, groupdim FROM sole_rugiada_log.misura124.solerugiada.vendita_referenza {code} The query above retrieves 18717 records. But if I remove some fields from the SELECT statements something goes wrong. Take for example the following query: {code:sql} SELECT codop, codref, data, quantita, fatturato FROM sole_rugiada_log.misura124.solerugiada.vendita_referenza {code} The above query gets only one record, which is a grouping over all the record, even if it doesn't include a GROUP BY clause. It's not clear what type of aggregation it does. It seems to be a sum of all records, but the result is not totally exact. The value of 'fatturato' is near the real sum (5043502.561000000 instead of 5046687.249000000), but the value of 'quantita' is much different from the real sum (489566 instead of 5537638). I noticed that removing the GROUP BY from the definition of the base table the problem disappears, but, of course, most of times this cannot be used as a workaround. Attached there are the project of the VDB and a log of the execution of the query that produces the wrong result. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
4
0 / 0

[JBoss JIRA] (TEIID-1790) Error parsing substring with non-simple expression

by Steven Hawkins (Created) (JIRA)

Error parsing substring with non-simple expression -------------------------------------------------- Key: TEIID-1790 URL: https://issues.jboss.org/browse/TEIID-1790 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 If the substring string expression is anything other than a single token the parser assumes ansi FROM ... FOR ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (TEIID-1824) SQL/XML performance enhancement

by Steven Hawkins (Created) (JIRA)

SQL/XML performance enhancement ------------------------------- Key: TEIID-1824 URL: https://issues.jboss.org/browse/TEIID-1824 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 The sql/xml processing functions, xmlforrest, xmlelement, xsltransform, etc. make use of stax factories by creating a newInstance each time. This is much too heavy-weight. The factories should be shared as much as possible. The woodstox input/ouput factories in particular can be static. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-1653) Support Cursoring over ODBC protocol ( support UseDeclareFetch = 1)

by Ramesh Reddy (JIRA)

Support Cursoring over ODBC protocol ( support UseDeclareFetch = 1) ------------------------------------------------------------------- Key: TEIID-1653 URL: https://issues.jboss.org/browse/TEIID-1653 Project: Teiid Issue Type: Feature Request Components: ODBC Affects Versions: 7.1.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.4.1, 7.5, 7.1.1 Postgres ODBC driver, retrieves all the rows from server for "select" request before it passes a single row to the calling client. This requires additional memory overhead for the client applications that dealing with very large resultset, which can lead to OOM issues. Postgres ODBC driver supports a couple properties UseDeclareFetch = 1 Fetch=1000 using which, ODBC driver will form the queries using postgres "cursor" functionality, and only fetch number of rows that are defined with variable "Fetch". This will result in faster initial response time to the user (especially UI based apps) because the driver is not fetching all rows, it is only fetching the first batch. Also, minimal memory foot print as it can clear the results as they are delivered to the client application, especially with FORWARD only cursor. Teiid will only support for FORWARD ONLY cursor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1825) EnhancementTimer class using the wrong logger class, results in errors accessing the Teiid through JDBC

by Ramesh Reddy (Created) (JIRA)

EnhancementTimer class using the wrong logger class, results in errors accessing the Teiid through JDBC ------------------------------------------------------------------------------------------------------- Key: TEIID-1825 URL: https://issues.jboss.org/browse/TEIID-1825 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.6 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.6 This class is using jboss logger, should be using the JDK logger. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
2
0 / 0

[JBoss JIRA] (TEIID-1847) Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1847?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1847. ----------------------------------- Assignee: Steven Hawkins Fix Version/s: (was: 7.6.1) Resolution: Out of Date I cannot reproduce this with other exceptions. CXF when converting faults does propagate the fault message to the exception thrown. This may not have been the case with Axis. Please reopen if this issue can be reproduced on Teiid. > Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-1847 > URL: https://issues.jboss.org/browse/TEIID-1847 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Labels: salesforce > > When encountering an UnexpectedErrorFault with com.sforce.soap.partner.SoapBindingStub.GetUpdated(), com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated() throws a null error message instead of the message returned from Salesforce. It appears that the getUpdated() method is using java.rmi.RemoteException.getMessage() when it should be using SFDC com.sforce.soap.partner.fault.ApiFault.getExceptionMessage() for "UnexpectedErrorFault" exceptions. Associated stack trace below. > [Salesforce Connector_1246|9725_Worker_106|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=5707647.13.7.333713 > ConnectorException: Status ERROR: com.metamatrix.core code=0 null > at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) > at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) > at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:275) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:141) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1847) Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1847?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1847: ---------------------------------- Fix Version/s: 7.6.1 (was: 8.0) > Salesforce connector does not report UnexpectedErrorFault exceptions correctly when calling getUpdated > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-1847 > URL: https://issues.jboss.org/browse/TEIID-1847 > Project: Teiid > Issue Type: Quality Risk > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Priority: Minor > Labels: salesforce > Fix For: 7.6.1 > > > When encountering an UnexpectedErrorFault with com.sforce.soap.partner.SoapBindingStub.GetUpdated(), com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated() throws a null error message instead of the message returned from Salesforce. It appears that the getUpdated() method is using java.rmi.RemoteException.getMessage() when it should be using SFDC com.sforce.soap.partner.fault.ApiFault.getExceptionMessage() for "UnexpectedErrorFault" exceptions. Associated stack trace below. > [Salesforce Connector_1246|9725_Worker_106|0] ERROR <CONNECTOR|0> Connector worker process failed for atomic-request=5707647.13.7.333713 > ConnectorException: Status ERROR: com.metamatrix.core code=0 null > at com.metamatrix.connector.salesforce.connection.SalesforceConnection.getUpdated(SalesforceConnection.java:737) > at com.metamatrix.connector.salesforce.execution.GetUpdatedExecutionImpl.execute(GetUpdatedExecutionImpl.java:65) > at com.metamatrix.connector.salesforce.execution.ProcedureExecutionParentImpl.execute(ProcedureExecutionParentImpl.java:86) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.processNewRequest(ConnectorWorker.java:275) > at com.metamatrix.dqp.internal.datamgr.impl.ConnectorWorker.process(ConnectorWorker.java:141) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 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 November 2011