August 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, https://bugzilla.redhat.com/show_bug.cgi?id=967982 (was: 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, 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

[JBoss JIRA] (TEIID-1311) Consider developing a connector/translator to Cassandra/Thrift

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1311?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1311: ---------------------------------- Priority: Major (was: Minor) See https://community.jboss.org/thread/231389 Radek has developed an initial solution which could be contributed back to the community. > Consider developing a connector/translator to Cassandra/Thrift > -------------------------------------------------------------- > > Key: TEIID-1311 > URL: https://issues.jboss.org/browse/TEIID-1311 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.1 > Environment: Any > Reporter: Ken Johnson > Fix For: Open To Community > > > Apache Cassandra is starting to see uptake beyond the big name social network players. Has any thought been given to offering connectivity to Cassandra through Teiid? Perhaps this is through consuming the Thrift file as metadata source. -- 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-1311) Consider developing a connector/translator to Cassandra/Thrift

by Ken Johnson (JIRA)

[ https://issues.jboss.org/browse/TEIID-1311?page=com.atlassian.jira.plugin... ] Ken Johnson commented on TEIID-1311: ------------------------------------ Bump. Cassandra support is seeing increasing demand. > Consider developing a connector/translator to Cassandra/Thrift > -------------------------------------------------------------- > > Key: TEIID-1311 > URL: https://issues.jboss.org/browse/TEIID-1311 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.1 > Environment: Any > Reporter: Ken Johnson > Priority: Minor > Fix For: Open To Community > > > Apache Cassandra is starting to see uptake beyond the big name social network players. Has any thought been given to offering connectivity to Cassandra through Teiid? Perhaps this is through consuming the Thrift file as metadata source. -- 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-2628) StackOverflowError Running Query Against REST Service

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2628?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2628: --------------------------------------- I should add that returning a buffer from xmltablenode is not thread safe as modifications are being made by the saxon processing. We may eventually add back similar logic but selectively return the buffer only when the full one is needed. > StackOverflowError Running Query Against REST Service > ----------------------------------------------------- > > Key: TEIID-2628 > URL: https://issues.jboss.org/browse/TEIID-2628 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Ted Jones > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > Attachments: flight-service-ds.xml, flight.vdb, flight.zip > > > When executing a query against https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/Fligh..., I get the following exception (with query plan included): https://gist.github.com/tejones/6250290 -- 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-2629) Message for missing translator needs improvement

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2629?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2629. ----------------------------------- Resolution: Done Consolidated the server/embedded handling and improved the message. > Message for missing translator needs improvement > ------------------------------------------------ > > Key: TEIID-2629 > URL: https://issues.jboss.org/browse/TEIID-2629 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine, Server > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > If a vdb references a non-existent translator type our message is not helpful - in embedded the exception message is the translator name and in the server we mention the vdb. -- 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-2629) Message for missing translator needs improvement

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2629: ------------------------------------- Summary: Message for missing translator needs improvement Key: TEIID-2629 URL: https://issues.jboss.org/browse/TEIID-2629 Project: Teiid Issue Type: Quality Risk Components: Query Engine, Server Affects Versions: 8.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 If a vdb references a non-existent translator type our message is not helpful - in embedded the exception message is the translator name and in the server we mention the vdb. -- 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-2628) StackOverflowError Running Query Against REST Service

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2628?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2628. ----------------------------------- Resolution: Done Fixed by removing the the use of the xmltablenode final buffer entirely and added assertions in the join logic to ensure that we don't use non-closed buffers (which can happen with dup-removal, but should never actually feed a join as we'll convert it to dup remove sort). > StackOverflowError Running Query Against REST Service > ----------------------------------------------------- > > Key: TEIID-2628 > URL: https://issues.jboss.org/browse/TEIID-2628 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Ted Jones > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > Attachments: flight-service-ds.xml, flight.vdb, flight.zip > > > When executing a query against https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/Fligh..., I get the following exception (with query plan included): https://gist.github.com/tejones/6250290 -- 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-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- Nice, I did not think about using the system tables. I will re-work and submit another patch. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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-2584) Add management features to materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2584: --------------------------------------- > 1) Currently both SYS and SYSADMIN are both categorized as "SOURCE" schemas, should I add another at "VIRTUAL" schema for this purpose? No that don't matter. A view in a source schema is still processed as a view. > 2) How can I look up metadata inside the virtual procedure? You have to lookup the oid, then lookup the property by name: {code} declare string uid = (select uid from sys.tables where schemaName = ... and name = ...); declare string propValue = (select "value" from sys.properties where sys.uid = variables.uid and name = ... ); {code} > I will rewrite using "merge" currently our merge won't work as you can't differentiate between an updated/inserted row. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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-2584) Add management features to materialization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- >You could use a single system procedure with dynamic sql by passing in just the fully qualified name (probably in parts) and then use system lookups for the metadata. Two questions on this (the reason why I went current route) 1) Currently both SYS and SYSADMIN are both categorized as "SOURCE" schemas, should I add another at "VIRTUAL" schema for this purpose? 2) How can I look up metadata inside the virtual procedure? To execute as system procedure in SYSADMIN, I could not fold all the needed statements like truncate/load/swap into single statement. I will rewrite using "merge". Also, since these are async loads I was not concerned about the performance hit. > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- 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