August 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2633) Criteria is assumed needed when no other predicates determined during RuleRaiseAccess

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2633: ------------------------------------ Summary: Criteria is assumed needed when no other predicates determined during RuleRaiseAccess Key: TEIID-2633 URL: https://issues.jboss.org/browse/TEIID-2633 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7.7 Reporter: Johnathon Lee Assignee: Steven Hawkins CanRaiseOverJoin method needs optimization in RuleRaiseAccess.java. A pushed join is assumed to need criteria based upon lack of predicates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2632) Atomic blocks don't reset the transaction context on completion

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2632?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2632. ----------------------------------- Resolution: Done Updated the commit/rollback methods on the TransactionServerImpl to appropriately clear the transaction state. > Atomic blocks don't reset the transaction context on completion > --------------------------------------------------------------- > > Key: TEIID-2632 > URL: https://issues.jboss.org/browse/TEIID-2632 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > > Once an atomic block has completed the transaction context remains as if it were a request level transaction. Further work, such as adding synchronizations, will result in exceptions as the txn has completed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2631) Issues with multiple returnable statements in a procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2631?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2631. ----------------------------------- Resolution: Done Allowing the implicit cursor to replace the old. > Issues with multiple returnable statements in a procedure > --------------------------------------------------------- > > Key: TEIID-2631 > URL: https://issues.jboss.org/browse/TEIID-2631 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > A regression was introduced by TEIID-2226 where any subsequent execution of a returnable statement in a procedure is effectively ignored: > begin > select ... > select ... > end > would not issue the second select unless all prior statements do not have result sets or are marked as without return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2632) Atomic blocks don't reset the transaction context on completion

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2632: ------------------------------------- Summary: Atomic blocks don't reset the transaction context on completion Key: TEIID-2632 URL: https://issues.jboss.org/browse/TEIID-2632 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.4.1, 8.5 Once an atomic block has completed the transaction context remains as if it were a request level transaction. Further work, such as adding synchronizations, will result in exceptions as the txn has completed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2630) SAP reponds with a 401 html page with bad or missing credentials

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2630?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2630. ----------------------------------- Fix Version/s: 8.4.1 8.5 Resolution: Done Refined the status code handling and added exceptions for 4xx + codes. > SAP reponds with a 401 html page with bad or missing credentials > ---------------------------------------------------------------- > > Key: TEIID-2630 > URL: https://issues.jboss.org/browse/TEIID-2630 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > With bad or missing credentials, SAP will respond back with an html page: > <html><head><title>Logon Error Message</title>... > which if passed into xmltable or other xml processing logic will give a parsing error, rather than an indication of what happened. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2631) Issues with multiple returnable statements in a procedure

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2631: ------------------------------------- Summary: Issues with multiple returnable statements in a procedure Key: TEIID-2631 URL: https://issues.jboss.org/browse/TEIID-2631 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 A regression was introduced by TEIID-2226 where any subsequent execution of a returnable statement in a procedure is effectively ignored: begin select ... select ... end would not issue the second select unless all prior statements do not have result sets or are marked as without return. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[Community] Announcement: Planed outage: 2013-08-24 5:00 PM UTC

by Libor Krzyžanek

Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] updated the announcement <b>Announcement</b>: "Planed outage: 2013-08-24 5:00 PM UTC" To view the announcement, visit: https://community.jboss.org/index.jspa -------------------------------------------------------------- Forums/Wiki/Blogs at community.jboss.org will be unavailable for about 4 hours due to upgrade. -------------------------------------------------------------- Announcement expires on August 28, 2013

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2630) SAP reponds with a 401 html page with bad or missing credentials

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2630: ------------------------------------- Summary: SAP reponds with a 401 html page with bad or missing credentials Key: TEIID-2630 URL: https://issues.jboss.org/browse/TEIID-2630 Project: Teiid Issue Type: Quality Risk Components: Misc. Connectors Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins With bad or missing credentials, SAP will respond back with an html page: <html><head><title>Logon Error Message</title>... which if passed into xmltable or other xml processing logic will give a parsing error, rather than an indication of what happened. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2263) makedep makenotdep hints should allow for more complicated scenarios

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2263?page=com.atlassian.jira.plugin... ] Work on TEIID-2263 started by Steven Hawkins. > makedep makenotdep hints should allow for more complicated scenarios > -------------------------------------------------------------------- > > Key: TEIID-2263 > URL: https://issues.jboss.org/browse/TEIID-2263 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > Attachments: dep.patch > > > In the option clause makedep and makenotdep take what are typically fully-qualified names and mark all matching tables/views in the query. This is not generally a good idea. We should allow for something akin to oracle global table syntax (view.)*table to drill down more specifically. Ideally we'd also account for subqueries and set operations as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2475: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 967982|https://bugzilla.redhat.com/show_bug.cgi?id=967982] from NEW to ASSIGNED > The RelationalNode.collectNodeStats is only subtracting out the last node > ------------------------------------------------------------------------- > > Key: TEIID-2475 > URL: https://issues.jboss.org/browse/TEIID-2475 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4, 7.7.8 > > Attachments: Query_Plan.txt > > > The "Node Cumulative Next Batch Process Time" Statistic > If you have a look at the explain plan (attached). Following the definition, > the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree. > The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2013