October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1288) Add support for explicit table syntax

by Steven Hawkins (JIRA)

Add support for explicit table syntax ------------------------------------- Key: TEIID-1288 URL: https://jira.jboss.org/browse/TEIID-1288 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 7.2 TABLE x should be a shortcut for SELECT * FROM x -- 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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1027) Use i18n for internationalization

by Van Halbert (JIRA)

Use i18n for internationalization ---------------------------------- Key: TEIID-1027 URL: https://jira.jboss.org/jira/browse/TEIID-1027 Project: Teiid Issue Type: Feature Request Components: Documentation, Server Affects Versions: 6.0.0 Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1 The components should be internationalized according to I18N standards. However, initially it will be limited to making the doc and product I18N available in English. -- 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, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (TEIID-1282) Teiid 7.0 Table columns not visible

by M A (JIRA)

Teiid 7.0 Table columns not visible ----------------------------------- Key: TEIID-1282 URL: https://jira.jboss.org/browse/TEIID-1282 Project: Teiid Issue Type: Bug Affects Versions: 7.0 Environment: Win 7, Eclipse Helio, squirrel Reporter: M A Assignee: Steven Hawkins Priority: Critical I am using teiid 7.0. It creates a VDB a related DS and works find for all the query execution, however when I connect to it : 1. Using squirrel, it does not displays the table columns for each VDB table. I have restarted the server, redeployed the VDB's and DS multiple times, but I am unable to view teh table columns. 2. Using java, when I try to create a clay diagram of teiid VDB, it shows me the tables... but no fields under it. Can you tell me how do I get to see the VDB table fields? Or any fix for this in teiid? -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1298) invalid links in Teiid Client Developer Guide

by Darrin Mison (JIRA)

invalid links in Teiid Client Developer Guide --------------------------------------------- Key: TEIID-1298 URL: https://jira.jboss.org/browse/TEIID-1298 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins <link linkend="document_validation">document validation</link> Table 3.2. Execution Properties "Determines whether XML documents returned by XML document models will be validated against their schema after processing. See the document validation section." The "document validation" link points to the same page as the link. The underlying XML here is: <para>Determines whether XML documents returned by XML document models will be validated against their schema after processing. See the <link linkend="document_validation">document validation</link> section.</para> There is no element with the id of "document_validation" -- 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

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1274) NPE during the execution of query when a wrong JNDI name supplied

by Ramesh Reddy (JIRA)

NPE during the execution of query when a wrong JNDI name supplied ----------------------------------------------------------------- Key: TEIID-1274 URL: https://jira.jboss.org/browse/TEIID-1274 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 java.lang.NullPointerException at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:99) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:72) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:124) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:121) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108) -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1292) Invalid Fetch Size using JDBC ODBC bridge to query MS Access via a Teiid VDB

by Warren Gibson (JIRA)

Invalid Fetch Size using JDBC ODBC bridge to query MS Access via a Teiid VDB ---------------------------------------------------------------------------- Key: TEIID-1292 URL: https://jira.jboss.org/browse/TEIID-1292 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steven Hawkins When using Squirrel as a client to query an Access DB with a Teiid VDB using the ODBC bridge I am getting an invalid Fetch Size. I have a DSN set up and can query the Access DB with an ODBC client using the DSN. There seems to be lots of chatter on the web about this but I didn't find a solution. This seems to be a KI with the JDBC ODBC bridge and is not a Teiid Bug but possibly Teiid can offer a workaround. 2010-10-05 15:52:17,421 DEBUG [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue16) Source-specific command: SELECT EmpData.LastName, EmpData.FirstName, EmpData.MiddleName, EmpData.EmpId, EmpData.Department, EmpData.AnnualSalary, EmpData.Title, EmpData.HomePhone, EmpData.Manager, EmpData.Street, EmpData.City, EmpData.State, EmpData.zip FROM EmpData 2010-10-05 15:52:17,421 DEBUG [org.teiid.COMMAND_LOG] (Worker3_QueryProcessorQueue16) ERROR SRC COMMAND: endTime=2010-10-05 15:52:17.421 requestID=o1eKkvzGMfT4.7 sourceCommandID=2 txID=null modelName=ODBCTesting connectorBindingName=jdbc-simple sessionID=o1eKkvzGMfT4 principal=admin@teiid-security finalRowCount=null 2010-10-05 15:52:17,421 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue16) Connector worker process failed for atomic-request=o1eKkvzGMfT4.7.2.1 [JDBCExecutionException] 0: Error Code:0 Message:'Invalid Fetch Size' error executing statement(s): [Prepared Values: [] SQL: SELECT EmpData.LastName, EmpData.FirstName, EmpData.MiddleName, EmpData.EmpId, EmpData.Department, EmpData.AnnualSalary, EmpData.Title, EmpData.HomePhone, EmpData.Manager, EmpData.Street, EmpData.City, EmpData.State, EmpData.zip FROM EmpData] 1 [SQLException]Invalid Fetch Size at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:88) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:263) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:281) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:71) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:123) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:120) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:108) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:189) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.sql.SQLException: Invalid Fetch Size at sun.jdbc.odbc.JdbcOdbcStatement.setFetchSize(Unknown Source) at org.jboss.resource.adapter.jdbc.WrappedStatement.setFetchSize(WrappedStatement.java:647) at org.teiid.translator.jdbc.JDBCBaseExecution.setSizeContraints(JDBCBaseExecution.java:138) at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:167) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:82) ... 12 more -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1259) Multi-line error message is difficult to follow

by Steven Hawkins (JIRA)

Multi-line error message is difficult to follow ----------------------------------------------- Key: TEIID-1259 URL: https://jira.jboss.org/browse/TEIID-1259 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 7.1.1 Errors with JDBC source queries are producing a multi-line error message that is hard to follow in the logs. -- 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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1258) fixed formatting of translators.xml in reference guide

by Darrin Mison (JIRA)

fixed formatting of translators.xml in reference guide ------------------------------------------------------ Key: TEIID-1258 URL: https://jira.jboss.org/browse/TEIID-1258 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.1 Reporter: Darrin Mison Assignee: Steven Hawkins The formatting of http://anonsvn.jboss.org/repos/teiid/branches/7.1.x/documentation/referen... made the XML very very hard to read. A patch is attached with the XML reformatted for readability. A few spelling mistakes have also been corrected. -- 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

14 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-1205) First deployment of weather example fails to query and requires restarting JBoss AS (weather does not exist)

by Paul Nittel (JIRA)

First deployment of weather example fails to query and requires restarting JBoss AS (weather does not exist) ------------------------------------------------------------------------------------------------------------ Key: TEIID-1205 URL: https://jira.jboss.org/browse/TEIID-1205 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Fedora 12, Teiid 7.1 CR2 Reporter: Paul Nittel Assignee: Steve Hawkins I started by installing JBoss AS and Teiid 7.1CR2 (plus JDBC drivers). After starting JBoss AS, I deployed the weather-ds and weather-vdb files. After seeing the VDB was "active" I used the simpleclient to execute this query: ./run.sh localhost 31000 weather "select t.* from (call weather.invoke(action='GET', endpoint=querystring('', '63017 10530' as zipCodeList, 'glance' as product, '2010-08-12T14:00:00' as \"begin\", '2010-08-12T14:00:00' as \"end\", 'maxt' as maxt, 'mint' as mint) )) w, XMLTABLE('/dwml/data/parameters' passing w.result columns Location string path '@applicable-location', TempName string path 'temperature/name', TempValue string path 'temperature/value' ) t" The result was: [QueryMetadataException]weather does not exist. at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:176) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.resolveSubQuery(SimpleQueryResolver.java:208) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:362) at org.teiid.query.sql.lang.SubqueryFromClause.acceptVisitor(SubqueryFromClause.java:127) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) at org.teiid.query.sql.navigator.AbstractNavigator.visitNodes(AbstractNavigator.java:73) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:259) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:523) at org.teiid.query.sql.lang.From.acceptVisitor(From.java:144) at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:62) at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:186) at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:103) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:174) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:126) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:100) at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:277) at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:378) at org.teiid.dqp.internal.process.Request.processRequest(Request.java:437) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:351) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:174) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) 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) Caused by: [QueryMetadataException]weather does not exist. at org.teiid.query.metadata.CompositeMetadataStore.getSchema(CompositeMetadataStore.java:65) at org.teiid.query.metadata.CompositeMetadataStore.getStoredProcedure(CompositeMetadataStore.java:108) at org.teiid.query.metadata.TransformationMetadata.getStoredProcedureInfoForProcedure(TransformationMetadata.java:300) at org.teiid.query.metadata.BasicQueryMetadataWrapper.getStoredProcedureInfoForProcedure(BasicQueryMetadataWrapper.java:273) at org.teiid.query.metadata.BasicQueryMetadataWrapper.getStoredProcedureInfoForProcedure(BasicQueryMetadataWrapper.java:273) at org.teiid.query.resolver.command.ExecResolver.findCommandMetadata(ExecResolver.java:79) at org.teiid.query.resolver.command.ExecResolver.resolveProceduralCommand(ExecResolver.java:246) at org.teiid.query.resolver.ProcedureContainerResolver.resolveCommand(ProcedureContainerResolver.java:195) at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:174) ... 26 more I shut down JBoss AS and restarted it and was able to execute the same query successfully. -- 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

14 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1297) Missing message key when no result for executes system procedure: "Request.no_result_set" in: org.teiid.query.i18n

by Ted Jones (JIRA)

Missing message key when no result for executes system procedure: "Request.no_result_set" in: org.teiid.query.i18n ------------------------------------------------------------------------------------------------------------------ Key: TEIID-1297 URL: https://jira.jboss.org/browse/TEIID-1297 Project: Teiid Issue Type: Bug Affects Versions: 7.1.1 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 7.1.1 Missing message key when no result for executes system procedure: WARN [PROCESSOR] Processing exception '<Missing message for key "Request.no_result_set" in: org.teiid.query.i18n>' for request c6cjFsmq1zcB.6. Exception type org.teiid.api.exception.query.QueryValidatorException thrown from org.teiid.dqp.internal.process.Request.createCommandContext(Request.java:222). Enable more detailed logging to see the entire stacktrace. -- 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

14 years, 2 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010