August 2010 - teiid-issues - Jboss List Archives

[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

14 years, 4 months

4
13
0 / 0

[JBoss JIRA] Created: (TEIID-1165) Upgrade to Netty 3.2.0 final

by Steve Hawkins (JIRA)

Upgrade to Netty 3.2.0 final ---------------------------- Key: TEIID-1165 URL: https://jira.jboss.org/browse/TEIID-1165 Project: Teiid Issue Type: Task Components: Server Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1174) Allow '-' character in VDB names.

by Barry LaFond (JIRA)

Allow '-' character in VDB names. --------------------------------- Key: TEIID-1174 URL: https://jira.jboss.org/browse/TEIID-1174 Project: Teiid Issue Type: Bug Reporter: Barry LaFond Assignee: Steve Hawkins Priority: Critical Teiid Designer is intending to use UUID prefixes for Preview VDB names. However, during development testing, the DTP connection fails because of the URL matcher for Teiid does not allow the '-' character. Sample Name: cfa01efb-34ea-43ab-b5cd-e29857150d4f_PartsTestProject_project.vdb -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1141) getCatalogs call on DatabaseMetadata is returning no rows

by Ramesh Reddy (JIRA)

getCatalogs call on DatabaseMetadata is returning no rows --------------------------------------------------------- Key: TEIID-1141 URL: https://jira.jboss.org/browse/TEIID-1141 Project: Teiid Issue Type: Bug Components: JDBC Driver Affects Versions: 7.0 Reporter: Ramesh Reddy Fix For: 7.1 The call on DatabaseMetadata object, "getCatalogs" is returning no rows. This should return VDB as the catalog name. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1154) Remove JDOM

by Steve Hawkins (JIRA)

Remove JDOM ----------- Key: TEIID-1154 URL: https://jira.jboss.org/browse/TEIID-1154 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 Our usage of JDOM is fairly light. It should be removed as a dependency to prevent possible dependency conflicts. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1158) Sybase CTC queries - Unexpected results when <null> involved

by Warren Gibson (JIRA)

Sybase CTC queries - Unexpected results when <null> involved ------------------------------------------------------------ Key: TEIID-1158 URL: https://jira.jboss.org/browse/TEIID-1158 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Teiid 7.1 and Sybase 12.5 as a source using pushdown capabilities Sybase URL: jdbc:sybase:Tds:slntds17.mm.atl2.redhat.com:5000/bqt2 Reporter: Warren Gibson Assignee: Steve Hawkins It appears we are handling <null> differently in Sybase 12.5. Results are being returned when <null> is involved and apparently in the past these were not returned. The following queries are not returning the expected results in query testing: Query 1 SELECT intkey, charvalue FROM BQT1.SmallA WHERE concat(stringkey, charvalue) = '10' ORDER BY intkey The expected results is: IntKey and CharValue 1 0 However, the following is being returned: IntKey CharValue 1 0 10 <null> Query 2 SELECT INTKEY, TIMEVALUE FROM BQT1.SmallA WHERE LEFT(TIMEVALUE, 1) = 0 ORDER BY INTKEY The expected results is: 21 rows Actual results returned: 24 rows As you can see from the following there are 3 nulls which would make the 24 (21+3). TimeValue 1900-01-01 00:00:00.0 1900-01-01 00:00:00.0 1900-01-01 00:00:00.0 1900-01-01 01:00:00.0 1900-01-01 01:00:00.0 1900-01-01 01:00:00.0 1900-01-01 02:00:00.0 1900-01-01 02:00:00.0 1900-01-01 03:00:00.0 1900-01-01 03:00:00.0 1900-01-01 04:00:00.0 1900-01-01 04:00:00.0 1900-01-01 05:00:00.0 1900-01-01 05:00:00.0 1900-01-01 06:00:00.0 1900-01-01 06:00:00.0 1900-01-01 07:00:00.0 1900-01-01 08:00:00.0 1900-01-01 08:00:00.0 1900-01-01 09:00:00.0 1900-01-01 09:00:00.0 1900-01-01 10:00:00.0 1900-01-01 10:00:00.0 1900-01-01 11:00:00.0 1900-01-01 11:00:00.0 1900-01-01 12:00:00.0 1900-01-01 12:00:00.0 1900-01-01 13:00:00.0 1900-01-01 13:00:00.0 1900-01-01 14:00:00.0 1900-01-01 14:00:00.0 1900-01-01 15:00:00.0 1900-01-01 16:00:00.0 1900-01-01 16:00:00.0 1900-01-01 17:00:00.0 1900-01-01 17:00:00.0 1900-01-01 18:00:00.0 1900-01-01 18:00:00.0 1900-01-01 19:00:00.0 1900-01-01 19:00:00.0 1900-01-01 20:00:00.0 1900-01-01 20:00:00.0 1900-01-01 21:00:00.0 1900-01-01 21:00:00.0 1900-01-01 22:00:00.0 1900-01-01 22:00:00.0 1900-01-01 23:00:00.0 <null> <null> <null> -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1145) Unable to deploy VDB with virtual BQT2 model

by Barry LaFond (JIRA)

Unable to deploy VDB with virtual BQT2 model -------------------------------------------- Key: TEIID-1145 URL: https://jira.jboss.org/browse/TEIID-1145 Project: Teiid Issue Type: Bug Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Steve Hawkins Priority: Blocker John Doyle attempted to import BQT2 and execute through a virtual model in a VDB. 1) Imported BQT2 and created source model in Designer 2) Created VDB with BQT2 and deployed to Teiid, was able to query through DTP 3) Created Virtual BQT2 model and created VDB with both models. 4) Exception deploying this VDB to Teiid. (SEE ATTACHED LOG) Note that this appears to work with other DB's. These BQT2 models, do contain columns that require the "builtInDatatypes.xsd". Unlike MMX VBD's, we aren't including this XML schema in each VDB. Since the BQT2 Source model deploys and queries fine without it, it's weird that a Virtual model which also required it is failing deployment. This is the only special circumstances I could find looking at the use-case and it may or may not be relevant. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1161) Remove commons-logging and log4j jar's from the Jboss deployment kit

by Van Halbert (JIRA)

Remove commons-logging and log4j jar's from the Jboss deployment kit -------------------------------------------------------------------- Key: TEIID-1161 URL: https://jira.jboss.org/browse/TEIID-1161 Project: Teiid Issue Type: Feature Request Components: Build/Kits Reporter: Van Halbert Assignee: Van Halbert Priority: Minor The commons-logging and log4j jars need to be removed from the JBoss deployment kit. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1123) Add the ability to get url values and call binary http services

by Steve Hawkins (JIRA)

Add the ability to get url values and call binary http services --------------------------------------------------------------- Key: TEIID-1123 URL: https://jira.jboss.org/browse/TEIID-1123 Project: Teiid Issue Type: Sub-task Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We should have the ability to get the value of a url and/or the ability to use the WSConnection to get a DataSource based dispatch for binary calls. The resulting blob can be converted to a clob using the decode function or to xml via the xmlparse 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, 4 months

1
2
0 / 0

[JBoss JIRA] Closed: (TEIID-1149) Importing tables from a deployed VDB does not import columns

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1149?page=com.atlassian.jira.plugin.s... ] Steve Hawkins closed TEIID-1149. -------------------------------- > Importing tables from a deployed VDB does not import columns > ------------------------------------------------------------ > > Key: TEIID-1149 > URL: https://jira.jboss.org/browse/TEIID-1149 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Assignee: Steve Hawkins > Priority: Critical > Fix For: 7.1 > > Attachments: NoColumns.png, TeiidDes-506Projects.zip > > > I created, and deployed, a VDB containing source and view models. I am able to query these tables. > I created a new project and into that project I attempted to import a view model's table from the previously-created VDB. What I found in the imported was the models and tables were shown, but no columns were available for import. Once imported, the tables did have no columns. > Screenshot and other stuff 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, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2010