August 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1168) Query Testing - CLOB, LOB, etc is returning an object reference in CTC rather than returning the content of the object (content is needed for validation purposes)

by Warren Gibson (JIRA)

Query Testing - CLOB, LOB, etc is returning an object reference in CTC rather than returning the content of the object (content is needed for validation purposes) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: TEIID-1168 URL: https://jira.jboss.org/browse/TEIID-1168 Project: Teiid Issue Type: Bug Components: Integration Tests Reporter: Warren Gibson Assignee: Van Halbert Query testing is returning an object reference for CLOB, LOB, etc. In the past these were returned as a string. They should be converted to a string so the content can be validated. Examples: Query: SELECT * FROM XQTDoc.BQTDocTestDocument > > <actual_queryResults> > <select> > <dataElement type="xml">xml</dataElement> > </select> > <table rowCount="1" columnCount="1"> > <tableRow> > <tableCell> > <object>org.teiid.core.types.SQLXMLImpl@be76c7</object> > </tableCell> > </tableRow> > </table> > </actual_queryResults> > > > <expected_queryResults> > <select> > <dataElement type="xml">xml</dataElement> > </select> > <table rowCount="1" columnCount="1"> > <tableRow> > <tableCell> > <string><?xml version="1.0" encoding="UTF-8"?><xqt:BQTDocTest xmlns:xqt="http://www.metamatrix.com/XQTSchema"><SingleRow><IntKey>0</IntKey><StringKey>0</StringKey><IntNum/><StringNum>-24</StringNum><FloatNum>-24.0</FloatNum><LongNum>-24</LongNum><DoubleNum>-24.0</DoubleNum><ByteNum>-128</ByteNum><DateValue>2000-01-01</DateValue><TimeValue>00:00:00</TimeValue><TimestampValue>2000-01-01 00:00:00.0</TimestampValue><BooleanValue>false</BooleanValue><CharValue>1</CharValue><ShortValue>-32768</ShortValue><BigIntegerValue>-24</BigIntegerValue><BigDecimalValue>-24</BigDecimalValue><ObjectValue>-24</ObjectValue></SingleRow><SingleRow><IntKey>1</IntKey><StringKey>1</StringKey><IntNum>-23</IntNum><StringNum/><FloatNum>-23.0</FloatNum><LongNum>-23</LongNum><DoubleNum>-23.0</DoubleNum><ByteNum>-127</ByteNum><DateValue>2000-01-02</DateValue><TimeValue>01:00:00</TimeValue><TimestampValue>2000-01-01 00:00:01.0</TimestampValue><BooleanValue>true< ...................... > -- 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, 12 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1091) Add remaining SQL/XML functions

by Steve Hawkins (JIRA)

Add remaining SQL/XML functions ------------------------------- Key: TEIID-1091 URL: https://jira.jboss.org/browse/TEIID-1091 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1138) Add support to call binary web services

by Steve Hawkins (JIRA)

Add support to call binary web services --------------------------------------- Key: TEIID-1138 URL: https://jira.jboss.org/browse/TEIID-1138 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins We should add support to call http web services that return binary results. One problem is that JBoss WS does not support DataSource based calls. -- 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
5
0 / 0

[JBoss JIRA] Created: (TEIID-1202) JOPR Console VDB View has couple usability issues

by Ramesh Reddy (JIRA)

JOPR Console VDB View has couple usability issues -------------------------------------------------- Key: TEIID-1202 URL: https://jira.jboss.org/browse/TEIID-1202 Project: Teiid Issue Type: Quality Risk Components: Jopr Plugin Reporter: Ramesh Reddy Assignee: Ted Jones Fix For: 7.1 1) Full Name is not required. Name and version is suffice 2) Status {UP, DOWN} is verbose and useful IMO. Status is already is shown by red X on the left nav. Also, in the summary page we are calling it "ACTIVE". This needs to be tidy up. 3) Connection Type - needs more explanation in the description. With out it is going confuse users. -- 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

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1210) Add support for non-unique indexes for materialized view tables

by Steve Hawkins (JIRA)

Add support for non-unique indexes for materialized view tables --------------------------------------------------------------- Key: TEIID-1210 URL: https://jira.jboss.org/browse/TEIID-1210 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Currently only a primary key index is created for internal materialized view tables. It would be good to allow non-unique indexes to be created for all other index/unique constraints on the view. This would also allow the user to approximate a function based index by adding an additional column to the view projecting the evaluated function. -- 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

[JBoss JIRA] Created: (TEIID-1230) TeiidDriver is used instead of MetaMatrixDriver during connection to the MM Server

by Warren Gibson (JIRA)

TeiidDriver is used instead of MetaMatrixDriver during connection to the MM Server ---------------------------------------------------------------------------------- Key: TEIID-1230 URL: https://jira.jboss.org/browse/TEIID-1230 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.1 Reporter: Warren Gibson Assignee: Steve Hawkins Fix For: 7.1 The URL from MM is supported in the Teiid, thus MM Driver fails to load if this is not available in the DriverManager driver order. Log attached. -- 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
5
0 / 0

[JBoss JIRA] Created: (TEIID-1233) VDB version from the file name is not being picked up

by Steve Hawkins (JIRA)

VDB version from the file name is not being picked up ----------------------------------------------------- Key: TEIID-1233 URL: https://jira.jboss.org/browse/TEIID-1233 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Critical The version parsing logic is incorrect. -- 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-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-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-1198) Allow specifying the VDB version as part of the VDB name in the JDBC URL connection string.

by Ramesh Reddy (JIRA)

Allow specifying the VDB version as part of the VDB name in the JDBC URL connection string. ------------------------------------------------------------------------------------------- Key: TEIID-1198 URL: https://jira.jboss.org/browse/TEIID-1198 Project: Teiid Issue Type: Sub-task Components: JDBC Driver Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1 Currently when a user connects to a VDB of particular version they use the format jdbc:teiid:<vdb>@mm://host:port;version=?;user=.. additionally support jdbc:teiid:<vdb.version>@mm://host:port;user=.. in which case both the above URL are same. This format is required by the ODBC client. As in ODBC the "Connection Settings" are called after the connection is made. The version information is required at the time of the connection. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2010