April 2010 - teiid-issues - Jboss List Archives

[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

14 years, 7 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

14 years, 7 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

14 years, 7 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

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-396) Authorization Provider can not deleted using the Admin API

by Ramesh Reddy (JIRA)

Authorization Provider can not deleted using the Admin API ---------------------------------------------------------- Key: TEIID-396 URL: https://jira.jboss.org/jira/browse/TEIID-396 Project: Teiid Issue Type: Feature Request Components: Console, Server Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Currently the addAuthorizationProvider is supported through the Admin API, however there is no corresponding "remove". This needs to be provided. -- 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

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-1068) Provide a single Connector, that represents the DS and Teiid Connector for JDBC sources.

by Ramesh Reddy (JIRA)

Provide a single Connector, that represents the DS and Teiid Connector for JDBC sources. ---------------------------------------------------------------------------------------- Key: TEIID-1068 URL: https://jira.jboss.org/jira/browse/TEIID-1068 Project: Teiid Issue Type: Sub-task Components: JDBC Connector, Query Engine Affects Versions: 7.0 Environment: 7.0 M3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 7.0 Currently for dealing with relational databases Teiid requires two separate JCA components. 1. Data source 2. Teiid Connection Factory to the Data Source above Teiid query engine talks to 2, which in turn talks to 1. In this scenario, 2 provides the query translation facilities + acts as the proxy connection for the 1. Complications arise, as 2 is exposed as managed connection as well as 1. To be transactionally correct the both managed connections must behave like one. Also, there is burden on the user to create two separate "-ds.xml" files to define a single Teiid Connector. Since for 2, JCA behaviour is not needed, this can be removed. Provide a way to define a single "-ds.xml" file that will create a data source as well as the connection factory. Make the connection factory a stateful connection, which holds on to the data source connection. Provide templates to create such CF + DS in single step. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-752) Errors with bulk updates

by Steven Hawkins (JIRA)

Errors with bulk updates ------------------------ Key: TEIID-752 URL: https://jira.jboss.org/jira/browse/TEIID-752 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 6.2.0 The bulk update logic is not correct JDBCBaseExecution is calling addBatch too many times, and JDBCUpdateExecution is determining the multivalued row count incorrectly (ClassCastException). -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-866) AdminShell is not able to handle SELECT * INTO #TEMP FROM foo; (statement does not return a result set)

by Paul Nittel (JIRA)

AdminShell is not able to handle SELECT * INTO #TEMP FROM foo; (statement does not return a result set) ------------------------------------------------------------------------------------------------------- Key: TEIID-866 URL: https://jira.jboss.org/jira/browse/TEIID-866 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 6.2.0 Environment: Fedora 10, 6.2 Stable (GA) Reporter: Paul Nittel Assignee: Steven Hawkins Here's the crux of the issue: select * into #temp from bqt1.smalla; // Error: // Uncaught Exception: TargetError : at Line: 165 : in file: URL: jar:file:/home/pnittel/teiid62/adminshell/lib/teiid-adminshell-6.2.0.jar!/scripts/jdbc.bsh : throw e ; Target exception: com.metamatrix.jdbc.MMSQLException: Statement does not return a result set. Steve H. put it this way: "The into clause turns the statement into an insert, which does not have a result set - it only returns an update count. It does seem like AdminShell should handle that case. It's probably doing some parsing of the command and expecting it to return a resultset..." This same statement works fine in SQL Explorer. -- 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

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-788) Change internal handling of insert with query expression

by Steven Hawkins (JIRA)

Change internal handling of insert with query expression -------------------------------------------------------- Key: TEIID-788 URL: https://jira.jboss.org/jira/browse/TEIID-788 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 An insert with a query expression should be our dominant internal model. Select into should be rewritten as it instead of the other way around. -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-853) Dynamic command projection should be positional

by Steven Hawkins (JIRA)

Dynamic command projection should be positional ----------------------------------------------- Key: TEIID-853 URL: https://jira.jboss.org/jira/browse/TEIID-853 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 Dynamic commands using the as clause should match with the dynamic command based upon position, rather than name. For example exec string 'select x, y ...' as a string, b string; should work since the right number of symbols are projected. -- 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

14 years, 7 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2010