June 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-189) Temp tables should maintain their costing metadata

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-189?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-189: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Temp tables should maintain their costing metadata > -------------------------------------------------- > > Key: TEIID-189 > URL: https://jira.jboss.org/jira/browse/TEIID-189 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.3.0 > > > Defect Tracker #24522: Temp table cardinality is currently only used for staging tables. It would also be generally useful for ad hoc queries to have the TempTableStoreImpl maintain the cardinality of the tables. Other costing information could actually be incorrect now (such as column min/max) depending upon what has been selected into a temp table. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-372) Queries of expired sessions persist "too long"

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-372?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-372. -------------------------------- Resolution: Out of Date In all of our initial server testing for 6.x this was not observed, so closing for now. > Queries of expired sessions persist "too long" > ---------------------------------------------- > > Key: TEIID-372 > URL: https://jira.jboss.org/jira/browse/TEIID-372 > Project: Teiid > Issue Type: Task > Components: Server > Affects Versions: 6.0.0 > Environment: All > Reporter: Paul Nittel > Fix For: 6.x > > > The Server Connection Test includes a test where a JDBC session is created in jdbcisql, and then jdbcisql is killed (CTRL-C). After 30 - 50 minutes, that session is expired by the system and it is removed from the Sessions panel in the Console. > I noticed some time later that a query, belonging to the now gone session, was still showing up in the Queries panel. Several others are also hanging around. One was submitted over 2 hours earlier. > Refreshing the Console's panels does not help. Stopping and starting the Console doesn't help, either. > The queries should be removed from the system at (roughly) the same time the session is expired, or terminates on its own. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-167) Enhancement: Connector Developer's Kit needs overhaul

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-167?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-167: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Enhancement: Connector Developer's Kit needs overhaul > ----------------------------------------------------- > > Key: TEIID-167 > URL: https://jira.jboss.org/jira/browse/TEIID-167 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Documentation > Affects Versions: 6.x > Reporter: Ramesh Reddy > Assignee: John Doyle > Fix For: 6.3.0 > > > Defect Tracker #24469: The CDK kit is based on the Command Shell framework, this needs to be moved to either MMSehll based or the Beanshell based framework, with better help system -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-93) when a fairly complex query is pushed down to the XML-HTTP Connector, it fails

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-93?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-93: -------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > when a fairly complex query is pushed down to the XML-HTTP Connector, it fails > ------------------------------------------------------------------------------ > > Key: TEIID-93 > URL: https://jira.jboss.org/jira/browse/TEIID-93 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #25059: when a fairly complex query is pushed down to the XML-HTTP > Connector, it fails > Need a lot more information. > OK, here's how to reproduce this issue (which we hit at Citi). Use the attached model project set in 5.5.1RC2 Designer, and use the response.xml attached with your standard xmltool.war tester. Then issue the following query from Designer: > >> > >> select H_RelationshipID, H_RelationshipName, H_HHID, H_TeamLeadName, H_TeamLeadID, H_MemberFirstName, H_MemberLastName, H_MemberAcctID, H_MemberFCName, H_MemberFCNum, H_HHLeadInd, H_MemberType, H_MemberRole, H_clientId, A_ADDR_TYPE, A_ADDR_SUB_TYPE, A_ADDR_SUB_NAME, A_ADDR_LINE1, A_ADDR_LINE2, A_ADDR_LINE3, A_ADDR_LINE4, A_ADDR_LINE5, A_ADDR_LINE6, A_ADDR_FLAG1, A_ADDR_FLAG2, A_ADDR_FLAG3, A_ADDR_FLAG4, A_ADDR_FLAG5, A_ADDR_FLAG6, A_CITY, A_ZIP, A_STATE_CODE, A_POSTAL_CODE, A_COUNTRY, A_ALTA_TYPE, A_EFF_DATE, A_EXP_DATE from "RPXMLTest"."CustRelnDataWS.WS.RetrieveCustRelnData.relnDataSingleTable" where A_ADDR_TYPE IN ('BA','AA') AND ((A_ADDR_TYPE IN('AA')) AND(NVL(A_ALTA_TYPE,'') = '')) > >> > >> This plans to the following source query being pushed to the connector: > >> > >> SELECT A_ALTA_TYPE, H_RelationshipID, H_RelationshipName, H_HHID, H_TeamLeadName, H_TeamLeadID, H_MemberFirstName, H_MemberLastName, H_MemberAcctID, H_MemberFCName, H_MemberFCNum, H_HHLeadInd, H_MemberType, H_MemberRole, H_clientId, A_ADDR_TYPE, A_ADDR_SUB_TYPE, A_ADDR_SUB_NAME, A_ADDR_LINE1, A_ADDR_LINE2, A_ADDR_LINE3, A_ADDR_LINE4, A_ADDR_LINE5, A_ADDR_LINE6, A_ADDR_FLAG1, A_ADDR_FLAG2, A_ADDR_FLAG3, A_ADDR_FLAG4, A_ADDR_FLAG5, A_ADDR_FLAG6, A_CITY, A_ZIP, A_STATE_CODE, A_POSTAL_CODE, A_COUNTRY, A_EFF_DATE, A_EXP_DATE FROM RPXMLTest.CustRelnDataWS.WS.RetrieveCustRelnData.relnDataSingleTable WHERE (A_ADDR_TYPE IN ('BA', 'AA')) AND (A_ADDR_TYPE = 'AA') > >> > >> Now, the criteria here says that A_ADDR_TYPE needs to be in the set of 'AA', 'BA', AND needs to be equal to 'AA'. So really only those "rows" where A_ADDR_TYPE='AA' should be returned. But instead the connector returns all rows where A_ADDR_TYPE is 'AA' or 'BA'. > >> > > > > This seems like it could be a defect in the way we hande IN criteria. Was there ever a case or defect on this? -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-166) SalesForce connector should support "OrCriteria" and "NotCriteria"

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-166?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-166. -------------------------------- Resolution: Duplicate Issue duplicates TEIID-556 > SalesForce connector should support "OrCriteria" and "NotCriteria" > ------------------------------------------------------------------ > > Key: TEIID-166 > URL: https://jira.jboss.org/jira/browse/TEIID-166 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.x > Environment: Windows 2003 Server, SF tech preview > Reporter: Michael Walker > Assignee: John Doyle > Fix For: 6.x > > > SalesForce SOQL supports "OR" and "NOT" criteria, but our connector does not. We should implement this functionality and add the capabilities, to increase performance. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-497) Modify SOAP War to Allow for Multiple Connection Type Support

by Ted Jones (JIRA)

Modify SOAP War to Allow for Multiple Connection Type Support ------------------------------------------------------------- Key: TEIID-497 URL: https://jira.jboss.org/jira/browse/TEIID-497 Project: Teiid Issue Type: Feature Request Reporter: Ted Jones Assignee: Steven Hawkins Currently, the SOAP war can only connect to the MMDriver. This precludes connection to an embedded Teiid instance. The connection pool and VDB resource logic needs to change to specify which connection type to use (JDBC, JNDI, ?) and format the connection URL accordingly. A properties file would be ideal for specifying the connection type and URL format rather than storing the information in the web.xml as we have in the past. This Jira is a result of the following posting in the Teiid forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225928#4225928 -- 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

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-185) Add Option For MTOM in Web Services

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-185?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-185. ---------------------------------- Resolution: Deferred Deferring all post 6.1.1 soap service issues > Add Option For MTOM in Web Services > ----------------------------------- > > Key: TEIID-185 > URL: https://jira.jboss.org/jira/browse/TEIID-185 > Project: Teiid > Issue Type: Feature Request > Components: SOAP Services > Affects Versions: 6.x > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24316: It would be great if we could add an option for Enterprise Web Service users to use Message Transmission Optimization Mechanism (MTOM). This would provide a means for them to handle very large result sets without the memory implications. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-221) WS-RM Support in Enterprise Web Services

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-221?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-221. ---------------------------------- Resolution: Deferred Deferring all post 6.1.1 soap service issues > WS-RM Support in Enterprise Web Services > ---------------------------------------- > > Key: TEIID-221 > URL: https://jira.jboss.org/jira/browse/TEIID-221 > Project: Teiid > Issue Type: Feature Request > Components: SOAP Services > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Priority: Minor > Fix For: 6.2.0 > > > Defect Tracker #24022: Need to test and document WS-RM with Axis2 in our Enterprise Web Services. Will require adding the Sandesha module to our distribution or documenting the steps on how to do this. ING is asking about our plans for WS-RM support in our roadmap, so we need to make sure this is done for 5.5/6.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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-277) Create Automated Test for Data Services Over JMS

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-277?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-277. ---------------------------------- Resolution: Deferred Deferring all post 6.1.1 soap service issues > Create Automated Test for Data Services Over JMS > ------------------------------------------------ > > Key: TEIID-277 > URL: https://jira.jboss.org/jira/browse/TEIID-277 > Project: Teiid > Issue Type: Task > Components: SOAP Services > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.2.0 > > > Need an automated test for testing our Data Services over JMS. Also, this would be a nice sample for our kit. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-637) Combine the setting of tmp, cache, buffer, and txn store locations.

by Steven Hawkins (JIRA)

Combine the setting of tmp, cache, buffer, and txn store locations. ------------------------------------------------------------------- Key: TEIID-637 URL: https://jira.jboss.org/jira/browse/TEIID-637 Project: Teiid Issue Type: Task Components: Embedded Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 We should just define the root work directory for all of the temporary information. That will make integration and cleanup a lot easier. The deploy.properties would for example use dqp.workdir=./work then cache, etc. would be located at ./work/<instance>/cache etc. -- 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

16 years, 10 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2009