May 2010 - teiid-issues - Jboss List Archives

[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-1062) Expose the Teiid Runtime Version as a ManagedOperation/ManagedProperty

by Ted Jones (JIRA)

Expose the Teiid Runtime Version as a ManagedOperation/ManagedProperty ---------------------------------------------------------------------- Key: TEIID-1062 URL: https://jira.jboss.org/jira/browse/TEIID-1062 Project: Teiid Issue Type: Feature Request Components: AdminApi Affects Versions: 7.0 Reporter: Ted Jones Assignee: Ramesh Reddy It would be helpful to have the version of the Teiid Runtime available so that it good be added as an informational trait in the Teiid Jopr plugin -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIID-1054) When running the control: View VDB Session, at the vdb level, the actions indicate its disabled

by Van Halbert (JIRA)

When running the control: View VDB Session, at the vdb level, the actions indicate its disabled ------------------------------------------------------------------------------------------------ Key: TEIID-1054 URL: https://jira.jboss.org/jira/browse/TEIID-1054 Project: Teiid Issue Type: Bug Components: Jopr Plugin Affects Versions: 7.0 Reporter: Van Halbert Assignee: Ted Jones When running the control: View VDB Session, at the vdb level, the actions indicate its disabled, displaying the following message in the action column: : This link is disabled as it is not nested within a JSF form. Note: this only displays until the page refreshes, then it disappears. -- 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-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-1063) PropertyDefinition.getPropertyTypeClassName() Should Always Return A Java Class Name

by Dan Florian (JIRA)

PropertyDefinition.getPropertyTypeClassName() Should Always Return A Java Class Name ------------------------------------------------------------------------------------ Key: TEIID-1063 URL: https://jira.jboss.org/jira/browse/TEIID-1063 Project: Teiid Issue Type: Bug Affects Versions: 7.0 Reporter: Dan Florian Assignee: Steven Hawkins Fix For: 7.0 PropertyDefinition.getPropertyTypeClassName() return value is inconsistent. Sometimes it is returning the primitive type name and other times it is returning the Java Class Name. For instance, the "prefill" property returns "java.lang.Boolean" whilst the "use-java-context" property returns "boolean." I have noticed the same issue with integer types so I assume all types have the same issue. This method should always return the Java Class Name. -- 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
5
0 / 0

[JBoss JIRA] Created: (TEIID-1065) PropertyDefinition.getDisplayName() Should Agree With The Display Name Shown In JON

by Dan Florian (JIRA)

PropertyDefinition.getDisplayName() Should Agree With The Display Name Shown In JON ----------------------------------------------------------------------------------- Key: TEIID-1065 URL: https://jira.jboss.org/jira/browse/TEIID-1065 Project: Teiid Issue Type: Bug Affects Versions: 7.0 Environment: Teiid 7.0 M3 Reporter: Dan Florian Assignee: Steven Hawkins Fix For: 7.0 The display names of properties should be the same between JON and TEIID. For instance, the "jmx-invoker-name" property is displayed in JON as "Jmx Invoker Name" but in the PropertyDefinition the display name is "jmxInvokerName." -- 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
8
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

[JBoss JIRA] Created: (TEIID-676) Document/test a means of creating service that executes ad-hoc SQL commands inTeiid

by Ted Jones (JIRA)

Document/test a means of creating service that executes ad-hoc SQL commands inTeiid ----------------------------------------------------------------------------------- Key: TEIID-676 URL: https://jira.jboss.org/jira/browse/TEIID-676 Project: Teiid Issue Type: Sub-task Components: Documentation Affects Versions: 6.1.0 Reporter: Ted Jones Assignee: Ted Jones Fix For: 6.2.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

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1073) Logging not working in Teiid Jopr Plugin

by Ted Jones (JIRA)

Logging not working in Teiid Jopr Plugin ---------------------------------------- Key: TEIID-1073 URL: https://jira.jboss.org/jira/browse/TEIID-1073 Project: Teiid Issue Type: Bug Reporter: Ted Jones Assignee: Steven Hawkins Some stuff goes to console but for the most part log messages are swallowed -- 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, 10 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2010