November 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-168) Refine caching behavior

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-168?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins closed TEIID-168. -------------------------------- > Refine caching behavior > ----------------------- > > Key: TEIID-168 > URL: https://jira.jboss.org/browse/TEIID-168 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector, Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.1 > > > Connector resultset caching should be replaced with relation and procedure caching. This would initially be backed by the buffermanager, based upon hints/costing, and be utilized by the planner rather than the resolver. It would be good if we also detected the level of determinism. > Query resultset caching should also be backed by the buffermanager. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1030) Provide ability to retrieve a VDB archive from ModeShape repository and then deploy the Teiid runtime.

by Van Halbert (JIRA)

Provide ability to retrieve a VDB archive from ModeShape repository and then deploy the Teiid runtime. ------------------------------------------------------------------------------------------------------ Key: TEIID-1030 URL: https://jira.jboss.org/jira/browse/TEIID-1030 Project: Teiid Issue Type: Feature Request Components: Jopr Plugin Reporter: Van Halbert Assignee: Ted Jones Fix For: 7.1 Provide the ability to retrieve VDB archives from ModeShape repository and then deployed to Teiid runtime -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1225) Reuse procedure plans

by Steve Hawkins (JIRA)

Reuse procedure plans --------------------- Key: TEIID-1225 URL: https://jira.jboss.org/browse/TEIID-1225 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Stored procedure plans should be reused as much as possible - not just if the client is using a prepared statement. -- 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

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1224) Stored Procedures - java exception being thrown relating to pre-evaluation of uncorrelated subqueries

by Warren Gibson (JIRA)

Stored Procedures - java exception being thrown relating to pre-evaluation of uncorrelated subqueries ----------------------------------------------------------------------------------------------------- Key: TEIID-1224 URL: https://jira.jboss.org/browse/TEIID-1224 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Teiid 7.1 Final Reporter: Warren Gibson Assignee: Steve Hawkins Several BQT Stored Procedures are returning "java.lang.ClassCastException: org.teiid.query.processor.relational.ProjectNode cannot be cast to org.teiid.query.processor.relational.AccessNode" An example of a failing query is: SELECT IntKey, IntNum FROM BQT2.MediumB WHERE IntNum = (EXEC SP.sp_count_rows_between(10, 20)) ORDER BY IntKey Log file for this query is attached. Engineering analysis indicates the issue is related pre-evaluation of uncorrelated subqueries. -- 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

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIID-1216) Cannot pass xml result from one select as critera to another select

by John Doyle (JIRA)

Cannot pass xml result from one select as critera to another select ------------------------------------------------------------------- Key: TEIID-1216 URL: https://jira.jboss.org/browse/TEIID-1216 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: Teiid 7.1 CR2 on RHEL 5 Reporter: John Doyle Assignee: Steve Hawkins I've created a VDB with procedures to create and parse XML, as wall as one to invoke the WS connector. SQL that unites them all into a single call passing the created XML into the invoke procedure is failing: SELECT t.* FROM table (EXEC cis.CountryInfoServiceXML.CapitalCity.create_CapitalCity('US')) AS request, table (EXEC CountryInfoService.invoke('SOAP11', '', request.xml_out, 'http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso')) AS response, table (EXEC cis.CountryInfoServiceXML.CapitalCity.extract_CapitalCityResponse(RESPONSE.result)) AS t; 13:23:02,501 ERROR [PROCESSOR] Unexpected exception for request wHnSpxDdmkGB.5 [TeiidComponentException] ERR.015.006.0033: Error Code:ERR.015.006.0033 Message:Unable to evaluate request.xml_out: No value was available at org.teiid.query.util.CommandContext.getFromContext(CommandContext.java:389) at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:629) -- 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

15 years, 5 months

3
3
0 / 0

[JBoss JIRA] Updated: (TEIID-979) Add pushdown support for sql/xml functions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-979?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-979: --------------------------------- Fix Version/s: 7.4 (was: 7.3) Pushing to 7.4 > Add pushdown support for sql/xml functions > ------------------------------------------ > > Key: TEIID-979 > URL: https://jira.jboss.org/browse/TEIID-979 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Connector > Affects Versions: 7.1 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 7.4 > > > We should have pushdown support for SQL/XML functionality. In particular Oracle and DB2 have support. > see also case 5715 -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-217?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-217: --------------------------------- Fix Version/s: 7.4 (was: 7.3) Pushing to 7.4 > LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-217 > URL: https://jira.jboss.org/browse/TEIID-217 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Michael Walker > Priority: Minor > Fix For: 7.4 > > > If an attribute appears more than once, we should have some way to return all values. Currently, we only return one value, with no rhyme, reason, or determinism as to which one gets returned. Implementing this is difficult when multiple attributes appear more than once, of course. But a simple example of where this problem rears it's head is in modeling LDAP groups. Groups typically have repeating attributes to represent each member, and it would be nice to query all members of a given group, but impossible to do so with the current logic. > A sophisticated solution would create a normalized view of a DN, breaking out multi-valued attributes into a separate table that could be joined by a primary key. A simple solution might allow attributes to be flagged as "multi-valued", in which case, they could be maintained in a single denormalized table that represents all values in the DN. > If we build an importer for LDAP, we should consider how to best handle this issue in the importer design. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-987) Problem regarding how often availability is called on the Facet

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-987?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-987: --------------------------------- Fix Version/s: 7.4 (was: 7.3) Pushing to 7.4 > Problem regarding how often availability is called on the Facet > --------------------------------------------------------------- > > Key: TEIID-987 > URL: https://jira.jboss.org/browse/TEIID-987 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.0 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 7.4 > > > There's a problem where the Facet (resource) availability is being checked about 5 times consecutively for every resource. There is an embedded jopr issue regarding this issue (EMBJOPR-129) > However, until this can be fixed, we might have to add a system property to handle how often to allow availability to be checked to limit the calls. Otherwise, this could a large processing overhead. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-225) LDAP Connector should use base DN for table as base DN for updates as well as queries

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-225?page=com.atlassian.jira.plugin.sy... ] Steven Hawkins updated TEIID-225: --------------------------------- Fix Version/s: 7.4 (was: 7.3) Pushing to 7.4 > LDAP Connector should use base DN for table as base DN for updates as well as queries > ------------------------------------------------------------------------------------- > > Key: TEIID-225 > URL: https://jira.jboss.org/browse/TEIID-225 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.3RC2 > Reporter: Greg Haber > Priority: Minor > Fix For: 7.4 > > > Ramesh had a great idea earlier today on the LDAP connector: > [Ramesh] Why not search base info along with PK information to build the unique > DN? That seems possible right? > [Greg] Yes, that is a great idea! I will put in a JIRA for that (small code change, changing name of "search base" to just "base", and doc change). Probably we should have both relative and fully qualified DNs accepted here. Note however that the base may be several levels higher up in the tree then where you want to put the entry, so the base DN may be "ou=people,dc=company,dc=com", with a relative DN of "uid=ghaber,ou=newyork" here. -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1344) Create a Separate Plugin for Embedded Jopr vs JON

by Van Halbert (JIRA)

Create a Separate Plugin for Embedded Jopr vs JON ------------------------------------------------- Key: TEIID-1344 URL: https://jira.jboss.org/browse/TEIID-1344 Project: Teiid Issue Type: Task Components: Build/Kits Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Need to change the build process to create two plugin in teiid-console. One for Embedded Jopr and one for JON due to different classloading mechanisms. -- 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

15 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2010