August 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2643) Create CLI script to setup default datasource that does not use in-memory, but persistence

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2643?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2643: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1000181|https://bugzilla.redhat.com/show_bug.cgi?id=1000181] from ASSIGNED to MODIFIED > Create CLI script to setup default datasource that does not use in-memory, but persistence > ------------------------------------------------------------------------------------------ > > Key: TEIID-2643 > URL: https://issues.jboss.org/browse/TEIID-2643 > Project: Teiid > Issue Type: Enhancement > Components: Dashboard > Reporter: Van Halbert > Assignee: Van Halbert > > The default datasource setup for dashboard should use persistence, instead of in-memory. -- 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

10 years, 8 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 ASSIGNED to MODIFIED > 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.1, 8.5 > > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2639) Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2639?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2639: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1000623|https://bugzilla.redhat.com/show_bug.cgi?id=1000623] from ASSIGNED to MODIFIED > Internally generated and user submitted anonymous blocks can't access temp tables from the surrounding scope > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-2639 > URL: https://issues.jboss.org/browse/TEIID-2639 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > While the blocks are resolved against the surrounding scope, when executed the procedure plan shields them from seeing the higher level scopes just as when a real procedure is executed. This results in temporary table 'temp' not found exceptions, for example with a non-simple view v and the delete: > delete from v where e2 = (select max(e2) from temp as z where e3 = z.e3) -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2645) Invalid vdb results in NPE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2645?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2645: ---------------------------------- Affects Version/s: 8.0 > Invalid vdb results in NPE > -------------------------- > > Key: TEIID-2645 > URL: https://issues.jboss.org/browse/TEIID-2645 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > If we don't find a vdb.xml file in a vdb we'll later incur an NPE. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2645) Invalid vdb results in NPE

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2645?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2645. ----------------------------------- Resolution: Done Improving messages with an invalid .vdb and non-active vdb. > Invalid vdb results in NPE > -------------------------- > > Key: TEIID-2645 > URL: https://issues.jboss.org/browse/TEIID-2645 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > If we don't find a vdb.xml file in a vdb we'll later incur an NPE. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2645) Invalid vdb results in NPE

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2645: ------------------------------------- Summary: Invalid vdb results in NPE Key: TEIID-2645 URL: https://issues.jboss.org/browse/TEIID-2645 Project: Teiid Issue Type: Quality Risk Components: Server Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 If we don't find a vdb.xml file in a vdb we'll later incur an NPE. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2641) improve transaction handling in procedures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2641?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2641: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1002208|https://bugzilla.redhat.com/show_bug.cgi?id=1002208] from NEW to ASSIGNED > improve transaction handling in procedures > ------------------------------------------ > > Key: TEIID-2641 > URL: https://issues.jboss.org/browse/TEIID-2641 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.5 > > > Atomic blocks do not have well-defined handling w.r.t. variable assignments and the implicit return cursor. In both cases the affects are currently non-atomic - the last assignment/cursor is effective even. > Also exception handling in an atomic block must result in an exception being thrown to guarantee the entire block atomicity. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2641) improve transaction handling in procedures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2641?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2641: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1002208 > improve transaction handling in procedures > ------------------------------------------ > > Key: TEIID-2641 > URL: https://issues.jboss.org/browse/TEIID-2641 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.5 > > > Atomic blocks do not have well-defined handling w.r.t. variable assignments and the implicit return cursor. In both cases the affects are currently non-atomic - the last assignment/cursor is effective even. > Also exception handling in an atomic block must result in an exception being thrown to guarantee the entire block atomicity. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2555) Support pushdown of entire dependent joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2555?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2555. ----------------------------------- Resolution: Done Marking as resolved since initial testing has been performed. Additional work such as new source hints, the creation of indexes, etc. will be handled as new issues. > Support pushdown of entire dependent joins > ------------------------------------------ > > Key: TEIID-2555 > URL: https://issues.jboss.org/browse/TEIID-2555 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > If the data volume is not too large then in many circumstances pushing down the entire independent side of the join to perform the entire join at the source can enhance performance. > This would likely be built upon TEIID-2249 to make use of a make dep hint option. It would also likely be an expansion of the common table pushdown logic - but will require more extensive planning changes as the default logic is geared toward only the equi-join columns. > It has also been requested that the default preference for pushdown be based upon the estimated data width. > There is an issue with the form of the plan as with the existing logic it would be nearly impossible to back out of the decision to perform the full pushdown (which is why a hint is initially preferable). -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2644) Support retrieving result sets from any out parameter

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2644: ------------------------------------- Summary: Support retrieving result sets from any out parameter Key: TEIID-2644 URL: https://issues.jboss.org/browse/TEIID-2644 Project: Teiid Issue Type: Enhancement Components: JDBC Connector Reporter: Steven Hawkins Assignee: Steven Hawkins Currently Teiid expects the driver (for example DataDirect) or in case of oracle the return parameter to be result set. In scenarios were a wrapping stored function cannot be created we should also offer support for retrieving any out parameter as the result set. -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2013