February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-137) Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-137?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-137: ------------------------------- Component/s: XML Connector Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Remove the HTTPClient Usage from the XML Connector and use the Common XML Connector > ----------------------------------------------------------------------------------- > > Key: TEIID-137 > URL: https://jira.jboss.org/jira/browse/TEIID-137 > Project: Teiid > Issue Type: Sub-task > Components: XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.0.0 > > > Need to remove the HTTPClient usage from the XML Connector and use the Axis client in the Common XML Connector to reduce download size -- 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-136) Determine when systeminit and systemshutdown should be called

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-136?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-136: ------------------------------- Component/s: Server Fix Version/s: 6.1.0 Affects Version/s: 6.1.0 > Determine when systeminit and systemshutdown should be called > ------------------------------------------------------------- > > Key: TEIID-136 > URL: https://jira.jboss.org/jira/browse/TEIID-136 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 6.1.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.1.0 > > > Due to other refactoring, MetaMatrixController calls to performSystemInit and indicateSystemShutdown used to control promotion of the configuration were removed. We need to rethink in general our strategy 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-127) Create a logging context specific to processing

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-127?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-127: ------------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Create a logging context specific to processing > ----------------------------------------------- > > Key: TEIID-127 > URL: https://jira.jboss.org/jira/browse/TEIID-127 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.0 > > > Currently processing (com.metamatrix.query.processor) exceptions are mapped to the planner context. Either everything needs to be DQP or a specific context is needed. -- 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-128) Consider replacing homegrown XML-Relational doc cache implementation with JBoss Cache or other standard implementation

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-128?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-128: ------------------------------- Component/s: XML Connector Fix Version/s: 6.1.0 Affects Version/s: 6.x > 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 > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-129) Implement or remove unused transactions panel from console

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-129?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-129: ------------------------------- Component/s: Console Fix Version/s: 6.1.0 Affects Version/s: 6.x > Implement or remove unused transactions panel from console > ---------------------------------------------------------- > > Key: TEIID-129 > URL: https://jira.jboss.org/jira/browse/TEIID-129 > Project: Teiid > Issue Type: Quality Risk > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > The console and admin api have stubs for administering transactions, which have not been implemented. See ServerTransaction, TransactionAdminApi, TransactionManager, 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

15 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-116?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-116: --------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour Fix Version/s: 6.0.0 (was: 7.x) Assignee: Steven Hawkins Complexity: Low > 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 > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.0.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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-124) insert with query should be supported at the connector level

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-124?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-124: ------------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > insert with query should be supported at the connector level > ------------------------------------------------------------ > > Key: TEIID-124 > URL: https://jira.jboss.org/jira/browse/TEIID-124 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #25005: Insert into with a query is now supported at the query level and is the ANSI standard way of representing select into. Insert with a query should become the dominant concept rather than select into, and it should be supported through the connector layer so that same source operations do not have the overhead of a select into. -- 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-119) physical procedural mapping results in inconsistent results

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-119?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-119: ------------------------------- Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > physical procedural mapping results in inconsistent results > ----------------------------------------------------------- > > Key: TEIID-119 > URL: https://jira.jboss.org/jira/browse/TEIID-119 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.1.0 > > > Defect Tracker #24951: testing a query with multiple physical procedure calls using the new mapping style results in inconsistent/incorrect results. As a test case, sptest6, a physical procedure that doubles the integer value passed into it, was called twice in a view transformation, with a result set consisting of the the source, input, and result values for each call to the procedure. 2 issues were seen: > 1) Source and input value columns only showed the value of the last input parameter for all rows. > 2) The result values for the first procedure call were correct for every row, but the result values for the second procedure call were the same for every row (it only showed the last result value calculated for all the rows). > After mapping the physical procedure to a virtual procedure, no issue was seen. Issue can be seen in "view.two_bqt_sptest6_test" in attached vdb, or at mm://sluxtech09:55391 (http://sluxtech09:18391). -- 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-226) Cacheing translated commands would improve connector performance

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-226?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-226: --------------------------------- Component/s: Connector API Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Complexity: High It would probably be best for TEIID-303 to be worked, with the addition of prepared commands (references in the data language) so that the command itself could be used as a cache key. > Cacheing translated commands would improve connector performance > ---------------------------------------------------------------- > > Key: TEIID-226 > URL: https://jira.jboss.org/jira/browse/TEIID-226 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #16722: AD 2/17/05 - Command translation in connector - approx. half the time taken to create an Execution object is spent in command translation. If there was a way to cache the translated command, then we could eliminate that step for subsequent requests. > Alex 2/17/05 - The problem is that the connector can be used with different vdbs, so the translation may be different even for the same query. Still seems do-able [...]. -- 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-122) Min/Max cardinality should be enforced during document generation

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-122?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-122: ------------------------------- Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Min/Max cardinality should be enforced during document generation > ----------------------------------------------------------------- > > Key: TEIID-122 > URL: https://jira.jboss.org/jira/browse/TEIID-122 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24334: Currently we do not use the min/max cardinality information at processing time to determine whether the document being built is schema compliant. We should instead throw exception when min is not met or max is exceeded. -- 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