June 2013 - teiid-issues - Jboss List Archives

[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 updated TEIID-2475: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=975035 (was: https://bugzilla.redhat.com/show_bug.cgi?id=975033, https://bugzilla.redhat.com/show_bug.cgi?id=975035) > 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 > > 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, 6 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 updated TEIID-2475: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=975033, https://bugzilla.redhat.com/show_bug.cgi?id=975035 (was: https://bugzilla.redhat.com/show_bug.cgi?id=975033) > 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 > > 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, 6 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: ------------------------------------------------ dsteigne(a)redhat.com made a comment on [bug 975035|https://bugzilla.redhat.com/show_bug.cgi?id=975035] Description of problem: 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) Version-Release number of selected component (if applicable): 5.3.1 > 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 > > 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, 6 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 updated TEIID-2475: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=975033 > 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 > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2249) Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-2249?page=com.atlassian.jira.plugin... ] Debbie Steigner edited comment on TEIID-2249 at 6/17/13 9:00 AM: ----------------------------------------------------------------- Customer RBS input: Hi Erica I had a read of the temp table documentation for Teiid 8.3 and I am unsure whether it meets our full requirement. It is a good start having the ability to create source temp table. As it stands, the temp table has to be predefined before the execution of the query and seems like have to be done in a teiid stored procedure. Our requirement, is the creation of source temp table will be done in the background by Teiid during runtime of a query and dependent join is pushed down to source to do the join locally at the source. It is basically shipping the temp data into target source for joining to improve the performance. It will be good if we can also hint the query to specify when to use this temp table join or set a threshold value if there are more than X no. Of values in IN clause switch to use this method. And potentially creating an index on the source temp table on the joining columns and also the ability to specify source system hints too. Thanks Nelson > Enable the use of temporary tables for those data sources that support them instead of IN criteria for EDS > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-2249 > URL: https://issues.jboss.org/browse/TEIID-2249 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > Our proposal is to allow for the more efficient use of large ad-hoc result-sets by rather than creating a long 'IN' list, inserting them in to a temporary table - for example a # table in Sybase and SQL Server - and then generating an SQL join to that instead. > One of the difference to materialized views (or at least my understanding), is that this work happens at a data-source rather than within the Teiid server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2527) Dynamically change the sources in a multi-source model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2527?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2527: ---------------------------------- Fix Version/s: 8.5 Estimated Difficulty: Medium Component/s: Query Engine Server Part of the original assumption behind the restriction is compiled plans and validation are built around a fixed notion of the sources available. We just need to tie the update mechanisms into the metadata update logic to appropriately flush plans. > Dynamically change the sources in a multi-source model > ------------------------------------------------------ > > Key: TEIID-2527 > URL: https://issues.jboss.org/browse/TEIID-2527 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, see https://community.jboss.org/message/821113 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2547) Fix drools-integration

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2547?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-2547. -------------------------------- Resolution: Done Updated quick start to change manually changing config to using CLI script and also updated the jboss-as-plugin version to 7.4. > Fix drools-integration > ---------------------- > > Key: TEIID-2547 > URL: https://issues.jboss.org/browse/TEIID-2547 > Project: Teiid > Issue Type: Sub-task > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > > Fix the .rar deployment based on the new EAP deployment requirements. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2547) Fix drools-integration

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2547?page=com.atlassian.jira.plugin... ] Work on TEIID-2547 stopped by Van Halbert. > Fix drools-integration > ---------------------- > > Key: TEIID-2547 > URL: https://issues.jboss.org/browse/TEIID-2547 > Project: Teiid > Issue Type: Sub-task > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > > Fix the .rar deployment based on the new EAP deployment requirements. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2552) Upgrade javacc-maven-plugin from 2.4.1 to 2.6

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2552?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2552. ----------------------------------- Fix Version/s: 8.4.1 8.5 Resolution: Done Changed the plug-in version to 2.6 (which you may need to remove if a managed value is being picked up else where) and adapted to the ParseException change by taking ownership of the class (which means that we could pull the exception related logic out of QueryParser into ParseException - but I did not take that step yet). Added a hack around JAVACC-244 by introducing a corrected method in the grammar file and using a source processing task to prevent the use of the broken method. A rather disquieting number of changes really. > Upgrade javacc-maven-plugin from 2.4.1 to 2.6 > --------------------------------------------- > > Key: TEIID-2552 > URL: https://issues.jboss.org/browse/TEIID-2552 > Project: Teiid > Issue Type: Component Upgrade > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.4.1, 8.5 > > > javacc-maven-plugin 2.6 is needed due to other components are already using 2.6. > Also, its already been determined that Teiid fails to compile when 2.6 is used. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2552) Upgrade javacc-maven-plugin from 2.4.1 to 2.6

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2552?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2552: --------------------------------------- So the compile problem is fairly straight-forward to fix as we can take ownership of the ParseException class, however the 2.6 maven plugin also introduces https://java.net/jira/browse/JAVACC-244 which causes meaningless error messages in some circumstances (one of which is in our unit tests). > Upgrade javacc-maven-plugin from 2.4.1 to 2.6 > --------------------------------------------- > > Key: TEIID-2552 > URL: https://issues.jboss.org/browse/TEIID-2552 > Project: Teiid > Issue Type: Component Upgrade > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > javacc-maven-plugin 2.6 is needed due to other components are already using 2.6. > Also, its already been determined that Teiid fails to compile when 2.6 is used. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2013