February 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-872) Add Teiid 6.2 release binaries in the JBoss Maven repository

by Ramesh Reddy (JIRA)

Add Teiid 6.2 release binaries in the JBoss Maven repository ------------------------------------------------------------ Key: TEIID-872 URL: https://jira.jboss.org/jira/browse/TEIID-872 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 6.2.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Priority: Minor Add 6.2 release to the JBoss Maven repository at http://repository.jboss.com/maven2/org/jboss/teiid/ -- 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

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-908) Enable access to the query plan without reference to Teiid classes.

by John Doyle (JIRA)

Enable access to the query plan without reference to Teiid classes. ------------------------------------------------------------------- Key: TEIID-908 URL: https://jira.jboss.org/jira/browse/TEIID-908 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 6.2.0 Environment: Eclipse Data Tools Platform connection to Teiid. Reporter: John Doyle Assignee: Steven Hawkins Eclipse Data Tools provides a framework for getting/displaying a query plan and I want to implement it as part of our DTP plug-ins. Currently you can only get the query plan from the MMStatement class, but DTP works only with the JDBC interfaces. Access to the query plan via the JDBC APIs and core java classes will enable us to plug into the framework. -- 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

13 years, 9 months

4
13
0 / 0

[JBoss JIRA] Created: (TEIID-874) Wiki documentation on SSL Encryption is misleading

by Nestor D. Rodriguez (JIRA)

Wiki documentation on SSL Encryption is misleading -------------------------------------------------- Key: TEIID-874 URL: https://jira.jboss.org/jira/browse/TEIID-874 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 6.2.0 Environment: N/A Reporter: Nestor D. Rodriguez Assignee: Steven Hawkins Priority: Minor The wiki page describing how to implement SSL in Teiid (https://www.jboss.org/community/wiki/secureclientconnectionsusingsslinteiid) implies that the keystore and trustore password properties (ssl.keystore.Password and ssl.truststore.Password) can be entered in cleartext. The code, on the other hand, requires them to be encrypted, using the strategy described in http://www.jboss.org/community/wiki/EncryptingpasswordsinTeiid The documentation needs to be modified to reflect that. -- 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

13 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-914) OnWrapTransactionTests.testMultipleSourceTimeout test fails due to due to execpted error message is different

by Van Halbert (JIRA)

OnWrapTransactionTests.testMultipleSourceTimeout test fails due to due to execpted error message is different ------------------------------------------------------------------------------------------------------------- Key: TEIID-914 URL: https://jira.jboss.org/jira/browse/TEIID-914 Project: Teiid Issue Type: Bug Components: Integration Tests Affects Versions: 7.0 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor The OnWrapTransactionTests.testMultipleSourceTimeout test fails due to expected message is different. It appears the upstream error being thrown by sendRequestMessageAndWait(..) in MMStatement.executeSql(String[] commands, boolean isBatchedCommand, Boolean requiresResultSet) has changed. If I take the message from the caught exception and prepend to the created message and use that message in the MMSQLException throw, then the test passes. Also, another problem with the current error message is that it gives no indication as to the problem why the statement cannot run, it only provides a general message, ilke the following: "Error trying to execute a statement [insert into pm1.g1 (e1, e2) values(600,'600'), insert into pm1.g2 (e1, e2) values (600,'600') .........." -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-831) Stored procedure execution fails with with out parameters after in

by Steven Hawkins (JIRA)

Stored procedure execution fails with with out parameters after in ------------------------------------------------------------------ Key: TEIID-831 URL: https://jira.jboss.org/jira/browse/TEIID-831 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Stored procedure execution, such as the fakemetadata pm2.sptest8 fail with with out parameters after in. This is due to skipping the index increment for in parameters. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-715) Allow the user to set null ordering behavior

by Steven Hawkins (JIRA)

Allow the user to set null ordering behavior -------------------------------------------- Key: TEIID-715 URL: https://jira.jboss.org/jira/browse/TEIID-715 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3.0 Sources that support order by may have different null ordering behavior than Teiid (which currently treats null as low). We should support the option for the server to be configured as nulls high, low, always high, or always low. Connectors will need to indicate the sort mode they support so the appropriate push-down and compensating actions can be taken. -- 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

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-765) Procedures without a return parameter and with output parameters indexing issue

by Steven Hawkins (JIRA)

Procedures without a return parameter and with output parameters indexing issue ------------------------------------------------------------------------------- Key: TEIID-765 URL: https://jira.jboss.org/jira/browse/TEIID-765 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Procedures without a return parameter and with output parameters index the output parameter(s) by +1 of what they should be. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-464) Shared Installation Option

by Ramesh Reddy (JIRA)

Shared Installation Option -------------------------- Key: TEIID-464 URL: https://jira.jboss.org/jira/browse/TEIID-464 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 We need to decide if/how we're going to support the shared installation option. With the changes to what's stored in the metamatrix.properties (i.e., host properties and config.name), this now complicates how we'll install (i.e., system host setup and odbc) / support this feature. -- 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

13 years, 9 months

5
19
0 / 0

[JBoss JIRA] Created: (TEIID-929) Virtual Procedure - IllegalArgumentException: Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl

by Warren Gibson (JIRA)

Virtual Procedure - IllegalArgumentException: Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-929 URL: https://jira.jboss.org/jira/browse/TEIID-929 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins They following virtual procedure is failing with an IllegalArumentException. Does "Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl" mean anything to you? This query does run in Designer. SELECT DNT FROM VirtProcs.vDate_n_Time WHERE intkey_in = 2" 2010-01-12 12:49:12,387 ERROR [Worker7_QueryProcessorQueue0] org.teiid.DQP - Unexpected exception for request 0.0 java.lang.IllegalArgumentException: Expected argument to be an instance of org.teiid.connector.metadata.runtime.Table; was instance of org.teiid.connector.metadata.runtime.ProcedureRecordImpl at com.metamatrix.core.util.ArgCheck.isInstanceOf(ArgCheck.java:353) at com.metamatrix.core.util.ArgCheck.isInstanceOf(ArgCheck.java:337) at org.teiid.metadata.TransformationMetadata.isXMLGroup(TransformationMetadata.java:701) at com.metamatrix.query.metadata.TempMetadataAdapter.isXMLGroup(TempMetadataAdapter.java:429) at com.metamatrix.query.metadata.TempMetadataAdapter.isXMLGroup(TempMetadataAdapter.java:429) at com.metamatrix.query.metadata.TempMetadataAdapter.isXMLGroup(TempMetadataAdapter.java:429) at com.metamatrix.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:297) at com.metamatrix.query.sql.lang.UnaryFromClause.acceptVisitor(UnaryFromClause.java:82) at com.metamatrix.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:61) at com.metamatrix.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:72) at com.metamatrix.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:246) at com.metamatrix.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:431) at com.metamatrix.query.sql.lang.From.acceptVisitor(From.java:143) at com.metamatrix.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:61) at com.metamatrix.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:177) at com.metamatrix.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:94) at com.metamatrix.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:176) at com.metamatrix.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:128) at com.metamatrix.query.optimizer.relational.RelationalPlanner.resolveVirtualGroup(RelationalPlanner.java:905) at com.metamatrix.query.optimizer.relational.RelationalPlanner.buildTree(RelationalPlanner.java:635) at com.metamatrix.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:553) at com.metamatrix.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:516) at com.metamatrix.query.optimizer.relational.RelationalPlanner.generatePlan(RelationalPlanner.java:393) at com.metamatrix.query.optimizer.relational.RelationalPlanner.optimize(RelationalPlanner.java:144) at com.metamatrix.query.optimizer.QueryOptimizer.optimizePlan(QueryOptimizer.java:109) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:470) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:556) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:336) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:176) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:44) at com.metamatrix.common.queue.WorkerPoolFactory$StatsCapturingSharedThreadPoolExecutor$1.run(WorkerPoolFactory.java:211) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- 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

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIID-753) MySQL translator issues

by Steven Hawkins (JIRA)

MySQL translator issues ----------------------- Key: TEIID-753 URL: https://jira.jboss.org/jira/browse/TEIID-753 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 MySQL does not change the autocommit flag to false when running in a global transaction, however the current autocommit detection logic does not take whether we're in an xa transaction into account. Also the timestamp literal format TIMESTAMP(...) actually produces a null value. This should be changed to either the jdbc escape syntax or simply the string literal form. -- 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

13 years, 9 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2010