May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-630) Add Support for UDDI V3 in WSDL Publishing Feature of Console

by Ted Jones (JIRA)

Add Support for UDDI V3 in WSDL Publishing Feature of Console ------------------------------------------------------------- Key: TEIID-630 URL: https://jira.jboss.org/jira/browse/TEIID-630 Project: Teiid Issue Type: Feature Request Components: Console Affects Versions: 6.0.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 6.2.0 We currently only support UDDI V2 in our UDDI publishing within our console. We need to be able to support both V2 and V3. -- 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

15 years

2
1
0 / 0

[JBoss JIRA] Resolved: (TEIID-636) Grouping node with dup removal has incorrect row count

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-636?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-636. ---------------------------------- Resolution: Done updated the row count after the sort. see TestGroupingNode > Grouping node with dup removal has incorrect row count > ------------------------------------------------------ > > Key: TEIID-636 > URL: https://jira.jboss.org/jira/browse/TEIID-636 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.1.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.1.0 > > > Grouping node with dup removal has incorrect row count, since the row count is not updated after the sort. -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-416) Create Hibernate Dialect for Teiid

by Ramesh Reddy (JIRA)

Create Hibernate Dialect for Teiid ---------------------------------- Key: TEIID-416 URL: https://jira.jboss.org/jira/browse/TEIID-416 Project: Teiid Issue Type: Feature Request Components: Build/Kits, JDBC Driver Affects Versions: 6.x Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 6.1.0 Create Hibernate dialect for Teiid. -- 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

15 years

2
4
0 / 0

[JBoss JIRA] Commented: (TEIID-401) Increase performance of XML-Relational connectors file cache

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-401?page=com.atlassian.jira.plug... ] John Doyle commented on TEIID-401: ---------------------------------- Because I was trying to solve the memory issue at the same time as the caching issue, I changed the XML parsing to a streaming parser at the same time I changed the cache. So it would be pretty difficult to determine how to divide out the performance improvement. That said, I have done some side by side testing 5.5.3 using directories of very large documents and the performance improvement is great. Minutes to seconds. > Increase performance of XML-Relational connectors file cache > ------------------------------------------------------------ > > Key: TEIID-401 > URL: https://jira.jboss.org/jira/browse/TEIID-401 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: John Doyle > Fix For: 6.1.0 > > > I-T 248339. XML-Relational File Connector has severe performance issues when forced to use file caching on Linux/Solaris OS. When using only the in-memory cache, the sample query in 248339 takes around 10 seconds. When using the file cache, the query takes around 270 seconds to complete. The sample data file source in 248339 consumes around 25MB of memory, so the default memory cache setting of 16MB forces the file cache to be used. -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-401) Increase performance of XML-Relational connectors file cache

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-401?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-401: ------------------------------------ I know we centralized the caching, such that it is very easy for us to distribute this cache contents, can you also see if there was any performance improvement with this implementation, compared to last versions when you get sometime?. I think that would be helpful validate this work too. Also, I have not done any perf checks on JBoss cache checks myself. Thanks. > Increase performance of XML-Relational connectors file cache > ------------------------------------------------------------ > > Key: TEIID-401 > URL: https://jira.jboss.org/jira/browse/TEIID-401 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: John Doyle > Fix For: 6.1.0 > > > I-T 248339. XML-Relational File Connector has severe performance issues when forced to use file caching on Linux/Solaris OS. When using only the in-memory cache, the sample query in 248339 takes around 10 seconds. When using the file cache, the query takes around 270 seconds to complete. The sample data file source in 248339 consumes around 25MB of memory, so the default memory cache setting of 16MB forces the file cache to be used. -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-401) Increase performance of XML-Relational connectors file cache

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-401?page=com.atlassian.jira.plug... ] John Doyle resolved TEIID-401. ------------------------------ Resolution: Done Done > Increase performance of XML-Relational connectors file cache > ------------------------------------------------------------ > > Key: TEIID-401 > URL: https://jira.jboss.org/jira/browse/TEIID-401 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: John Doyle > Fix For: 6.1.0 > > > I-T 248339. XML-Relational File Connector has severe performance issues when forced to use file caching on Linux/Solaris OS. When using only the in-memory cache, the sample query in 248339 takes around 10 seconds. When using the file cache, the query takes around 270 seconds to complete. The sample data file source in 248339 consumes around 25MB of memory, so the default memory cache setting of 16MB forces the file cache to be used. -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-128) Consider replacing homegrown XML-Relational doc cache implementation with JBoss Cache or other standard implementation

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-128?page=com.atlassian.jira.plug... ] John Doyle resolved TEIID-128. ------------------------------ Resolution: Done Done > Consider replacing homegrown XML-Relational doc cache implementation with JBoss Cache or other standard implementation > ---------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-128 > URL: https://jira.jboss.org/jira/browse/TEIID-128 > Project: Teiid > Issue Type: Quality Risk > Components: XML Connector > Affects Versions: 6.x > Reporter: Greg Haber > Assignee: John Doyle > Priority: Minor > Fix For: 6.1.0 > > > My understanding is that the document cache implementation in the XML-Relational connector is a homegrown implementation. Homegrown = more code to maintain and better chance of us hitting major issues like JBEDSP-834. Plus AFAIK this homegrown cache implementation locks the whole cache even on read operations which I suspect is going to introduce scaling problems (in fact I think we actually experienced this at a customer with 5.0SP2 but we were unable to conclusively determine that that was the cause of problems we saw then). -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-626) Eclipse Datatools view cannot see tables in a VDB

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-626?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-626: ------------------------------------ Assignee: Steven Hawkins (was: Ramesh Reddy) Our returned value for table type are not upper capped, which is what Data tools is expecting. Other issues: Our procedures are showing up, however they are under user defined, rather than stored procedures. Running connect without first doing a ping runs the chance of their ui using two different class versions of the embeddeddriver. This causes two dqps to be created. That second instance runs into problems with the JBossCache JMX registration, since it's using the same instance name as the first. We need to ensure that everything with a global reach (JMX, filesystem) uses the instance name / workspace dir to differentiate itself from other instances in the same vm. > Eclipse Datatools view cannot see tables in a VDB > ------------------------------------------------- > > Key: TEIID-626 > URL: https://jira.jboss.org/jira/browse/TEIID-626 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.0.0 > Environment: Connected to mm://slntmm06.mm.atl2.redhat.com:50201 using the SQL Development Tools perspective in Eclipse versions 3.3.2 and 3.4, and JBoss DevStudio. Tested both the 5.5.2 and 5.5.3 JDBC drivers for MetaMatrix. > Reporter: Steve Jacobs > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > The Eclipse Datatools Project provides a "Database Development" perspective that we will be using in Westport to replace our SQL Explorer perspective. The "Data Source Explorer" view can connect to a VDB in MetaMatrix, but the Tables are not being shown. Please investigate what JDBC calls are being made to popluate this view and fix our driver so the view may be populated correctly. -- 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

15 years

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-590) Embedded has classloading issues with JBoss AS

by Ramesh Reddy (JIRA)

Embedded has classloading issues with JBoss AS ---------------------------------------------- Key: TEIID-590 URL: https://jira.jboss.org/jira/browse/TEIID-590 Project: Teiid Issue Type: Bug Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Critical Fix For: 6.1.0 Since Teiid uses the same libraries as JBoss Cache, JBoss TS, and JGroups, there are version incompatibilities that needs to be dealt with. This JIRA should provide guidance as to how to deploy into 4.2.2 and 5.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

15 years

2
4
0 / 0

[JBoss JIRA] Moved: (TEIID-626) Eclipse Datatools view cannot see tables in a VDB

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-626?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-451 to TEIID-626: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-626 (was: JBEDSP-451) Component/s: JDBC Driver (was: JDBC) Fix Version/s: 6.1.0 (was: Westport) Affects Version/s: 6.0.0 (was: 5.5.2) > Eclipse Datatools view cannot see tables in a VDB > ------------------------------------------------- > > Key: TEIID-626 > URL: https://jira.jboss.org/jira/browse/TEIID-626 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.0.0 > Environment: Connected to mm://slntmm06.mm.atl2.redhat.com:50201 using the SQL Development Tools perspective in Eclipse versions 3.3.2 and 3.4, and JBoss DevStudio. Tested both the 5.5.2 and 5.5.3 JDBC drivers for MetaMatrix. > Reporter: Steve Jacobs > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > The Eclipse Datatools Project provides a "Database Development" perspective that we will be using in Westport to replace our SQL Explorer perspective. The "Data Source Explorer" view can connect to a VDB in MetaMatrix, but the Tables are not being shown. Please investigate what JDBC calls are being made to popluate this view and fix our driver so the view may be populated correctly. -- 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

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009