February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-123) Staging tables performance appears to be sub-par

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-123?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-123: ------------------------------- Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Staging tables performance appears to be sub-par > ------------------------------------------------ > > Key: TEIID-123 > URL: https://jira.jboss.org/jira/browse/TEIID-123 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.x > > > Defect Tracker #20207: While working on the E2E Staging Tables Test Script, Mark Donnelly noticed the performance was fairly even between docs using staging tables and docs not using staging tables. I did further research and found the queries ran faster without staging tables. The email thread is attached (zipped in case the Trakka doesn't like it). > The Model Project Set is also attached. The VDB's lone binding is defined. -- 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, 10 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/jira/browse/TEIID-225?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-225: --------------------------------- Component/s: LDAP Connector Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > 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/jira/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 > Assignee: Greg Haber > Priority: Minor > Fix For: 6.1.0 > > > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-112) Need to add SAML support to Data Services

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-112?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-112: ------------------------------- Component/s: SOAP Services Fix Version/s: 6.x Affects Version/s: 6.x > Need to add SAML support to Data Services > ----------------------------------------- > > Key: TEIID-112 > URL: https://jira.jboss.org/jira/browse/TEIID-112 > Project: Teiid > Issue Type: Bug > Components: SOAP Services > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 6.x > > > Defect Tracker #24253: Need to provide a means to pass SAML assertions into the server for authorization. The token will be passed via the payload token. For release 5.5, a custom membership domain will have access to the SAML assertion and will be able to process accordingly. Future releases will have a built-in process for using the SAML assertions. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-113) Connector Bindings Window requires refresh to see newly imported Connectors

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-113?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-113: ------------------------------- Component/s: Console Fix Version/s: 6.1.0 Affects Version/s: 6.x > Connector Bindings Window requires refresh to see newly imported Connectors > --------------------------------------------------------------------------- > > Key: TEIID-113 > URL: https://jira.jboss.org/jira/browse/TEIID-113 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #22555: 1. Imported Parts.vdb > 2. On step 6 of Virtual Database Import Wizard I unchecked Set Status Active and Synchronize and clicked > Finish. > 3. VDB appeared as inactive. > 4. The two connector Bindings I just imported with the vdb were not present in the Integration > Server/Connector Bindings window. > 5. Had to do a refresh to see the new connector bindings. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-114) Execs of xml procedures cannot be used as correlated scalar subqueries

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-114?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-114: ------------------------------- Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Execs of xml procedures cannot be used as correlated scalar subqueries > ---------------------------------------------------------------------- > > Key: TEIID-114 > URL: https://jira.jboss.org/jira/browse/TEIID-114 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24364: attempted to run select (exec BooksInfo.getXMLBooksByEdition(edition)) result from booksinfo.booksinfo from the e2e audiobooks and received the following error: > java.lang.NullPointerException > at com.metamatrix.query.processor.xml.RelationalPlanExecutor.<init>(RelationalPlanExecutor.java:67) > at com.metamatrix.query.processor.xml.XMLProcessorEnvironment.createResultExecutor(XMLProcessorEnvironment.java:213) > at com.metamatrix.query.processor.xml.ExecSqlInstruction.process(ExecSqlInstruction.java:35) > at com.metamatrix.query.processor.xml.XMLPlan.getNextXMLChunk(XMLPlan.java:320) > at com.metamatrix.query.processor.xml.XMLPlan.processXML(XMLPlan.java:256) > at com.metamatrix.query.processor.xml.XMLPlan.nextBatch(XMLPlan.java:187) > at com.metamatrix.query.processor.relational.SubqueryProcessorUtility.process(SubqueryProcessorUtility.java:231) > at com.metamatrix.query.processor.relational.DependentProjectNode.prepareToProcessTuple(DependentProjectNode.java:96) > at com.metamatrix.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:200) > at com.metamatrix.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:244) > at com.metamatrix.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:143) > at com.metamatrix.query.processor.QueryProcessor.process(QueryProcessor.java:194) > at com.metamatrix.dqp.internal.process.ProcessWorker.processDirect(ProcessWorker.java:159) > at com.metamatrix.dqp.internal.process.ProcessWorker.process(ProcessWorker.java:89) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-116) Limit clause does not work with XML queries

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-116?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-116: ------------------------------- Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Limit clause does not work with XML queries > ------------------------------------------- > > Key: TEIID-116 > URL: https://jira.jboss.org/jira/browse/TEIID-116 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24430: Limit clause does not work with XML queries it probably should probably work the same as specifying the rowlimit function on the root mapping class(es) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-108) SOAP/XML Connectors should convert to the column type specified in WS request table

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-108?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-108: ------------------------------- Component/s: XML Connector Fix Version/s: 6.x Affects Version/s: 6.x > SOAP/XML Connectors should convert to the column type specified in WS request table > ----------------------------------------------------------------------------------- > > Key: TEIID-108 > URL: https://jira.jboss.org/jira/browse/TEIID-108 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.x > > > Defect Tracker #23654: [This came from our consultant Jimmy Fernandez' Case 4795, for customer MITRE]. > Jimmy wrote: "When modeling Web Services with our Web Service to relational importer and the column type on the request table out are dateTime objects; the SOAP/XML connectors should be converting the specific column to the xsd:dateTime object specifications. It would not hurt to ensure that we are following the correct specification for other xsd objects as well." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-103) Salesforce Connector: Count(*) did not appear to pushdown to SOQL.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-103?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-103: ------------------------------- Component/s: Salesforce Connector Fix Version/s: 6.x Affects Version/s: 6.x > Salesforce Connector: Count(*) did not appear to pushdown to SOQL. > ------------------------------------------------------------------ > > Key: TEIID-103 > URL: https://jira.jboss.org/jira/browse/TEIID-103 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 6.x > Reporter: John Doyle > Assignee: John Doyle > Priority: Minor > Fix For: 6.x > > > Count(*) did not appear to pushdown to SOQL. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-104) Connector development documentation out-of-date

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-104?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-104: ------------------------------- Component/s: Connector API Documentation Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Connector development documentation out-of-date > ----------------------------------------------- > > Key: TEIID-104 > URL: https://jira.jboss.org/jira/browse/TEIID-104 > Project: Teiid > Issue Type: Bug > Components: Connector API, Documentation > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > The included diagrams and documentation are not up-to-date with the limit, intersect, and except features. Documentation needs to be added for GlobalCapabilitiesProvider as well. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-105) MySQL capabilities should be made specific to version 4/5

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-105?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-105: ------------------------------- Component/s: JDBC Connector Fix Version/s: 6.1.0 Affects Version/s: 6.x > MySQL capabilities should be made specific to version 4/5 > --------------------------------------------------------- > > Key: TEIID-105 > URL: https://jira.jboss.org/jira/browse/TEIID-105 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #24746: The current mysql capabilities seem to have been written for version 5 (it initially included support for timestampdiff). The support for 4.x should be specifically refined or specifically removed from the docs. 4.x goes completely eol by the end of 2009, so it's unlikely many customers would care if this were done for 5.5.1. > see also http://www.mysql.com/company/legal/lifecycle/#calendar -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009