December 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-1392) Memory leak in Teiid

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1392?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-2674 to TEIID-1392: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1392 (was: SOA-2674) Affects Version/s: 7.1.1 (was: 5.1.0.ER5) Security: (was: JBoss Internal) Component/s: Server (was: EDS) > Memory leak in Teiid > -------------------- > > Key: TEIID-1392 > URL: https://issues.jboss.org/browse/TEIID-1392 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.1.1 > Reporter: Pavel Macik > Assignee: Van Halbert > Priority: Blocker > Attachments: 510ER5-eds_long_select_100t-overview.jps, eds-qs.zip > > > To reproduce: > 1.) unzip eds-qs.zip into ${SOA-P}/jboss-as/samples/quickstarts/ directory > 2.) copy/move ${EDS-QS}/build.properties-example to ${EDS-QS}/build.properties > 3.) the QS deploys a VDB with 2 Oracle10g datasources (you can configure (via build.properties) both to the same DB instance) > 4.) start the server up > 5.) using JDBC with following configuration send following SQL: > JDBC: > - URL: jdbc:teiid:perf@mm://${soa-p bind address}:31000 > - driver: org.teiid.jdbc.TeiidDriver > - username/password: according to ${SOA-P}/jboss-as/server/${profile}/conf/props/teiid-security-users.properties > SQL: > select * from perf.long.persons where person_id < 100 > With server max heap set to 3G the GC caused by the leak affects the server after cca 150k iterations -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1391) Changes to the use of SSL when connecting with the Teiid Driver are ignored after a successful connection

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1391?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-2663 to TEIID-1391: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1391 (was: SOA-2663) Affects Version/s: 7.1.1 (was: 5.1.0.ER5) Security: (was: Public) Component/s: JDBC Driver (was: EDS) > Changes to the use of SSL when connecting with the Teiid Driver are ignored after a successful connection > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-1391 > URL: https://issues.jboss.org/browse/TEIID-1391 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 7.1.1 > Reporter: John Verhaeg > > This might be a bit hard to follow, but... > I tried to execute a Teiid VDB from the Teiid Designer perspective, which asks me to create a Teiid connection profile, which displays the Teiid driver properties dialog. Not knowing whether the server I was using was configured for SSL, I went ahead and selected the SSL option and hit Test. It failed (as expected). I then unchecked that checkbox, retested, and the test ping succeeded. But then I re-checked the box and tried once more. It succeeded again (Huh?). I then hit Finish, and got a failure message after being transferred to the DTP perspective. Seeing the connection profile in the Data Source Explorer, I opened its context menu, which showed an option to disconnect (implying it was still in a connected state). I disconnected and then tried to reconnect. Again, that worked. Opening the connection's profile and changing its SSL setting has no effect after that. Only if I completely remove the connection and recreate it can I see the SSL option fail again, but only until I turn it off and get the connection to succeed. Thereafter the setting seems to once again be ignored. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIID-1389) Add additional detection for conflicting criteria to help optimize query plan

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1389?page=com.atlassian.jira.plugin... ] Steven Hawkins moved JBEDSP-1255 to TEIID-1389: ----------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-1389 (was: JBEDSP-1255) Affects Version/s: 6.0.0 (was: 5.5.4) Component/s: Query Engine (was: Server) > Add additional detection for conflicting criteria to help optimize query plan > ----------------------------------------------------------------------------- > > Key: TEIID-1389 > URL: https://issues.jboss.org/browse/TEIID-1389 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Add additional detection for conflicting criteria such as "(column1=1 OR column1=2) AND column1=3". The attempted use case was a case of a UNION that was using the column as a measure of selecting a specific datasource, with each query joined by the UNION having a specific set of column1 values (such as "column1=1 OR column1=2"). In the case of the end user application submitting criteria such as "column1=3", the query planner should prune any branches of the UNION with a conflicting set of values for column1. It would also be helpful if other operators such as <, >, <>, IN, etc. could be accounted for. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1090) Request to add a Google Apps/Calendar Connector

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1090?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1090: ---------------------------------- Fix Version/s: 7.4 (was: 7.3) pushing to 7.4 > Request to add a Google Apps/Calendar Connector > ------------------------------------------------ > > Key: TEIID-1090 > URL: https://issues.jboss.org/browse/TEIID-1090 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Fix For: 7.4 > > > Customer is requesting that we add a MetaMatrix Google Apps/Calendar Connector to a future release. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-245?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-245: --------------------------------- Fix Version/s: 7.4 (was: 7.3) pushing to 7.4 > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://issues.jboss.org/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.4 > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-219: --------------------------------- Fix Version/s: 7.4 (was: 7.3) pushing to 7.4 > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 7.4 > > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-89. --------------------------------- Resolution: Done updated the data role logic to account for temp tables. also updated the config to have system wide setting that allows for usage of temp tables by default. this is to be backwards compatible with the other 7.x release, but will allow users to configure their server as deny by default if they want. > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://issues.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-89) Data roles should account for the ability to create temp tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-89?page=com.atlassian.jira.plugin.s... ] Steven Hawkins commented on TEIID-89: ------------------------------------- In thinking about this more, it seems like we should be more explicit. Following mysql both create/drop and all dml statements should be covered by something like the CREATE_TEMPORARY_TABLES permission type. However the way our datapolicy logic works, it will be simpler to implement as an attribute of the policy (like anyauthenticated). Done this way there is no confusion or potential conflicts, but we will have to update the designer logic to add another check box. > Data roles should account for the ability to create temp tables > --------------------------------------------------------------- > > Key: TEIID-89 > URL: https://issues.jboss.org/browse/TEIID-89 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 7.3 > > > Defect Tracker #24698: Data roles should account for creating temp tables. Right now all temp table creation is allowed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1384) Partial Results processing fails too easily when a source is unavailable

by Van Halbert (JIRA)

Partial Results processing fails too easily when a source is unavailable ------------------------------------------------------------------------ Key: TEIID-1384 URL: https://jira.jboss.org/browse/TEIID-1384 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Environment: Fedora 12, SOA-P ER4 Reporter: Paul Nittel Assignee: Steven Hawkins I'm updating the MMx partial results test to work with Teiid and ran into this problem while testing that. To mimic an unavailable data source, I munged the server name in the data source definition (-ds) file. Using SQuirreL, I first "set partialResultsMode true" and then query a unioned table: SELECT * FROM PartialVM.MyUnionTable order by INTKEY. I'm getting back an exception about the bad connection, but no apparent attempt to continue the query without that source is made. Steve Hawkins suspects, "it's testing partial results at too low of a level". Artifacts will be attached. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
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

13 years, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2010