May 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-921) Queries containing a UNION with an ORDER BY are producing unexpected results in CTC Query Testing

by Warren Gibson (JIRA)

Queries containing a UNION with an ORDER BY are producing unexpected results in CTC Query Testing -------------------------------------------------------------------------------------------------- Key: TEIID-921 URL: https://jira.jboss.org/jira/browse/TEIID-921 Project: Teiid Issue Type: Bug Components: Integration Tests Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins I am getting unexpected results (all sources) on 17 queries containing a UNION and ORDER BY. The ORDER BY isn't working when there is a UNION involved. These queries were producing expected results prior to the holidays. Below is a sample query: RDBMS_Test_Queries_6500_TestQuery32" value="SELECT StringKey FROM BQT1.SmallA WHERE IntKey >= 0 AND IntKey < 15 UNION SELECT StringKey FROM BQT1.SmallB WHERE IntKey >= 10 AND IntKey < 30 ORDER BY StringKey DESC The interesting thing is the queries do work with a UNION ALL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-790) Teiid Server uses Sun JDK specific MX server, thus portability to other JDKs is not possible

by Ramesh Reddy (JIRA)

Teiid Server uses Sun JDK specific MX server, thus portability to other JDKs is not possible -------------------------------------------------------------------------------------------- Key: TEIID-790 URL: https://jira.jboss.org/jira/browse/TEIID-790 Project: Teiid Issue Type: Task Components: Server Affects Versions: 6.2.0 Reporter: Ramesh Reddy Priority: Critical Fix For: 6.3.0 Teiid Server assumes the JMX server is the one that is provided by the SUN JDK, thus if user uses other JDK implementations like Iced-tea it will not be supported. This dependency must be removed. Possibly need to use other independent open source based JMX servers like MX4J or JBoss MC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-881) SOAP Connector should expose property to control HTTP Header Transfer-Encoding: chunked

by Larry O'Leary (JIRA)

SOAP Connector should expose property to control HTTP Header Transfer-Encoding: chunked --------------------------------------------------------------------------------------- Key: TEIID-881 URL: https://jira.jboss.org/jira/browse/TEIID-881 Project: Teiid Issue Type: Feature Request Components: XML Connector Affects Versions: 6.2.0, 6.1.0, 6.0.0 Reporter: Larry O'Leary Assignee: Steven Hawkins A user has reported that results from a SOAP service using the SOAP-Relational connector are sometimes invalid. This is due to the results from an earlier invocation being returned. After further investigation this turned out to be a bug with the web server that was hosting the web service and its inability to properly handle chunked requests. By default, Axis 1.3/2 (not sure what we are using lately) uses chunked Transfer-Encoding. By disabling chunked transfer encoding it allows the faulty web server to properly serve the request and return the expected results. Ideally, chunked requests should be used as per the default Axis configuration but we should expose a means of overriding this behaviour in the event a user runs across a buggy web server. For example, in SOAPExecutor chunked requests can be enabled/disabled via a setting in the Call properties. Boolean isChunked = ((HTTPConnectorState) this.getState()).isHttpHeaderTransferEncodingChunked(); if (isChunked != null) { Hashtable httpProps = (Hashtable) call.getProperty(HTTPConstants.REQUEST_HEADERS); if (httpProps == null) { httpProps = new Hashtable(); } httpProps.put(HTTPConstants.HEADER_TRANSFER_ENCODING_CHUNKED, isChunked); call.setProperty(HTTPConstants.REQUEST_HEADERS, httpProps); } Please note, this code was written against Axis 1.3 which is used in XML-Relational SOAP Connector for MMx 5.5.3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-1019) Request ability to turn on/off Auto Staging tables

by Debbie Steigner (JIRA)

Request ability to turn on/off Auto Staging tables -------------------------------------------------- Key: TEIID-1019 URL: https://jira.jboss.org/jira/browse/TEIID-1019 Project: Teiid Issue Type: Feature Request Components: Server, XML Planner/Processor Reporter: Debbie Steigner Assignee: Steven Hawkins Fix For: 7.0 Please add the ability to turn on/off Auto Staging tables. Setting the Cardinality to 0 is not always a workaround if the customer wants the cardinality set for better query planning on other models. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (TEIID-940) COUNT function in Postgres push down producting exception

by Warren Gibson (JIRA)

COUNT function in Postgres push down producting exception --------------------------------------------------------- Key: TEIID-940 URL: https://jira.jboss.org/jira/browse/TEIID-940 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Postgres push down is producing unexpected CTC results with queries containing COUNT(*). Example: RDBMS_Test_Queries_4500_TestQuery69" value="SELECT COUNT(*) FROM BQT1.SmallA Error: com.metamatrix.api.exception.MetaMatrixComponentException SQLState: 38000 ErrorCode: 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-878) Fix capabilities caching

by Steven Hawkins (JIRA)

Fix capabilities caching ------------------------ Key: TEIID-878 URL: https://jira.jboss.org/jira/browse/TEIID-878 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 The caching of connector capabilities should be closer to the data layer to ensure that capabilities changes are picked up with connector restarts irregardless of vdb state. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-789) Provide JMX access from remote computers

by Ramesh Reddy (JIRA)

Provide JMX access from remote computers ---------------------------------------- Key: TEIID-789 URL: https://jira.jboss.org/jira/browse/TEIID-789 Project: Teiid Issue Type: Feature Request Components: Common Affects Versions: 6.2.0 Reporter: Ramesh Reddy Fix For: 6.3.0 Currently the JMX connection to Teiid Server is only available to local connections, connections from remote are not supported. Security is reason that remote connections are not allowed in the current implementation. Provide the security using JAAS, such that it hooks into the Membership implementation (recommended) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1067) Managed connector connection factory always closes the physical connection.

by Ramesh Reddy (JIRA)

Managed connector connection factory always closes the physical connection. ---------------------------------------------------------------------------- Key: TEIID-1067 URL: https://jira.jboss.org/jira/browse/TEIID-1067 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 7.0 As of 7.0 M3, the Connector's managed connection closes its physical connection each time the connection is released to the pool. This way the physical connection is not pooled at all and goes through unnecessary connection creation close for each query. The Managed connection should keep a stateful physical connection for the duration of its life. If the MC is destroyed then the phycal connection can be closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-857) MalformedURLException when connecting to teiid vdb.

by John Doyle (JIRA)

MalformedURLException when connecting to teiid vdb. --------------------------------------------------- Key: TEIID-857 URL: https://jira.jboss.org/jira/browse/TEIID-857 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.2.0 Environment: Teiid 6.2 embedded using the filepath configuration. Reporter: John Doyle Assignee: Steven Hawkins I'm not getting a log file from Teiid. I've just dropped a VDB into an unmodified 6.2 image and get the following when connecting. log4j:ERROR Could not parse url [mmfile:/home/jdoyle/NotBackedUp/teiid-6.2.0/deploy/log4j.xml]. java.net.MalformedURLException: unknown protocol: mmfile at java.net.URL.<init>(URL.java:574) at java.net.URL.<init>(URL.java:464) at java.net.URL.<init>(URL.java:413) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:650) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180) at org.apache.log4j.xml.DOMConfigurator$2.parse(DOMConfigurator.java:612) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:711) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:470) at org.apache.log4j.LogManager.<clinit>(LogManager.java:122) at org.apache.log4j.Logger.getLogger(Logger.java:104) at com.metamatrix.jdbc.Log4JUtil.getLogger(Log4JUtil.java:91) at com.metamatrix.jdbc.LogConfigurationProvider$Log4JLogConfiguration.isEnabled(LogConfigurationProvider.java:74) at com.metamatrix.common.log.LogManager.isMessageToBeRecorded(LogManager.java:358) at com.metamatrix.common.log.LogManager.logMessage(LogManager.java:364) at com.metamatrix.common.log.LogManager.logInfo(LogManager.java:214) at com.metamatrix.dqp.embedded.DQPEmbeddedPlugin.logInfo(DQPEmbeddedPlugin.java:71) at com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.initializeService(EmbeddedConfigurationService.java:975) at com.metamatrix.dqp.embedded.services.EmbeddedBaseDQPService.initialize(EmbeddedBaseDQPService.java:60) at org.teiid.dqp.internal.process.DQPCore.start(DQPCore.java:615) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIID-937) Request ability on client jar to set the ConnectionRetryCount and Delay

by Debbie Steigner (JIRA)

Request ability on client jar to set the ConnectionRetryCount and Delay ----------------------------------------------------------------------- Key: TEIID-937 URL: https://jira.jboss.org/jira/browse/TEIID-937 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Reporter: Debbie Steigner Assignee: Steven Hawkins Fix For: 7.0 In the current version of MetaMatrix, our client jdbc driver (metamatrix-jdbc.jar) has a hard-coded connection retry count of 3. Can this property be exposed so the customer can set the ConnectionRetryCount and the ConnectionRetryDelay. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2010