July 2010 - teiid-issues - Jboss List Archives

[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, 10 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, 10 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, 10 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, 10 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, 10 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, 10 months

2
2
0 / 0

[JBoss JIRA] Resolved: (TEIID-48) Better metadata for ODBC and materialization tables

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-48?page=com.atlassian.jira.plugin.sys... ] Steve Hawkins resolved TEIID-48. -------------------------------- Fix Version/s: 7.0 (was: 8.x) Resolution: Out of Date Both the ODBC and materialization implementations have changed. > Better metadata for ODBC and materialization tables > --------------------------------------------------- > > Key: TEIID-48 > URL: https://jira.jboss.org/browse/TEIID-48 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.0 > > > Materialization model and ODBC tables are currently visible in the metadata tree for all users. This is not desirable, but may be necessary since some clients should have that metadata. > At the very least we should be marking these as system tables. At best we would filter metadata based upon permissions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-962) Create new system function to dump temp table contents to file.

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-962?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-962: -------------------------------- Fix Version/s: 7.2 (was: 7.1) Pushing to 7.2. The workaround starting in 7.0 is to use the File translator saveFile procedure and SQLXML to produce an xml document form of the results. e.g. <file model>.saveFile('newFile.xml', (select xmlelement("root", xmlagg(xmlelement("row", xmlforest(c1, c2, c3 ...)))) from table )) that would save the document: <root> <row><c1>val</c1><c2>val</c2>...</row> ... </root> > Create new system function to dump temp table contents to file. > ----------------------------------------------------------------- > > Key: TEIID-962 > URL: https://jira.jboss.org/browse/TEIID-962 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Environment: All > Reporter: Ken Johnson > Assignee: Steve Hawkins > Fix For: 7.2 > > > A requirement to produce a CSV file reflecting the contents of a query result set so it can be subsequently FTP'd or email'd. In Nov 07 implemented this feature using the exec connector, a shell script and mods to JDBCISQL. > Suggested capability: function will take the following parameters: > - Temp table name as string > - Target file name (path qualified) as string > - Delimiter as string > When invoked, the specified temp table contents will be written out to the specified file using the specified delimiter to separate the column values. > This generic capability will allow the CSV file thats needed and subsequently process it with other UDF functionality as necessary. > Open questions: > 1. How does file path behave in a clustered environment? Is it relative to the MM Server install dir or fully qualified? > Suggest this feature remain undocumented for the short term. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-123) Staging tables performance appears to be sub-par

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-123?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-123: ------------------------------------- Temporary tables can now have primary keys, which could address some of the problems - if staging tables/mapping classes are allowed in the designer to set primary keys. > Staging tables performance appears to be sub-par > ------------------------------------------------ > > Key: TEIID-123 > URL: https://jira.jboss.org/browse/TEIID-123 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Fix For: 8.x > > > Defect Tracker #20207: While working on the E2E Staging Tables Test Script, Mark Donnelly noticed the performance was fairly even between docs using staging tables and docs not using staging tables. I did further research and found the queries ran faster without staging tables. The email thread is attached (zipped in case the Trakka doesn't like it). > The Model Project Set is also attached. The VDB's lone binding is defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-189) Temp tables should maintain their costing metadata

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-189?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins commented on TEIID-189: ------------------------------------- Added cardinality updates for session level temp tables. > Temp tables should maintain their costing metadata > -------------------------------------------------- > > Key: TEIID-189 > URL: https://jira.jboss.org/browse/TEIID-189 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.2 > > > Defect Tracker #24522: Temp table cardinality is currently only used for staging tables. It would also be generally useful for ad hoc queries to have the TempTableStoreImpl maintain the cardinality of the tables. Other costing information could actually be incorrect now (such as column min/max) depending upon what has been selected into a temp table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2010