November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-511) Make process plans serizializable.

by Steven Hawkins (JIRA)

Make process plans serizializable. ---------------------------------- Key: TEIID-511 URL: https://jira.jboss.org/jira/browse/TEIID-511 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.x Processing plans should be serializable to take advantage of replication and non-memory caches. See also TEIID-81 -- 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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] (TEIID-194) LDAP Connector should be deterministic about what value is returned when an attribute is multi-valued

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-194?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-194. ---------------------------------- Fix Version/s: (was: 9.x) Resolution: Won't Fix Resolving as won't fix as per Greg's comment since we do now allow for pulling all values as a concatenated string. > LDAP Connector should be deterministic about what value is returned when an attribute is multi-valued > ----------------------------------------------------------------------------------------------------- > > Key: TEIID-194 > URL: https://issues.jboss.org/browse/TEIID-194 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 9.x > Reporter: Michael Walker > Priority: Minor > > The LDAP connector returns only one result for a multi-valued attribute. It does not make any attempt to return the same value in a deterministic way, but should do so. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-403) ESB transport capabilitiy for connector framework

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-403?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-403: --------------------------------- Assignee: (was: Jerry Helbling) > ESB transport capabilitiy for connector framework > ------------------------------------------------- > > Key: TEIID-403 > URL: https://issues.jboss.org/browse/TEIID-403 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Fix For: 9.x > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-141) Develop a strategy for backtracking during planning

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-141?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-141. ---------------------------------- Fix Version/s: (was: 9.x) Resolution: Deferred Join planning already allows for some upward movement of criteria. We'll revisit this when needed by the community. > Develop a strategy for backtracking during planning > --------------------------------------------------- > > Key: TEIID-141 > URL: https://issues.jboss.org/browse/TEIID-141 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently rule raise access is run after rule push criteria, which can cause non-pushable criteria to end up in undesirable points of the plan. It would be good to either run rule raise access before the first run of push select criteria, or allow rule raise access to detect what nodes it can "push up". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-319) LDAP Connector should re-implement algorithm for translating SQL to LDAP search, using Visitor design pattern

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-319?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-319: --------------------------------- Fix Version/s: (was: 9.x) > LDAP Connector should re-implement algorithm for translating SQL to LDAP search, using Visitor design pattern > ------------------------------------------------------------------------------------------------------------- > > Key: TEIID-319 > URL: https://issues.jboss.org/browse/TEIID-319 > Project: Teiid > Issue Type: Task > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Priority: Optional > > Though the current approach works, it would be cleaner if the LDAP Connector used the Visitor design pattern to handle each part of a SQL query, and translate it into an LDAP search. This may make future changes easier to implement, and keep the code cleaner. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-219) Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value

by Steven Hawkins (Work stopped) (JIRA)

[ https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin.... ] Work on TEIID-219 stopped by Steven Hawkins. > Add a way to limit or suppress queries that exceed a threshold Cost-Based Optimizer value > ----------------------------------------------------------------------------------------- > > Key: TEIID-219 > URL: https://issues.jboss.org/browse/TEIID-219 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Client requesting an ability to impose a limit on, or suppress, any query that exceeds a cost estimate value specified by the user/administrator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1752) JavaDocs for Teiid needs to contain only what's exposed.

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1752?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1752: --------------------------------------- Changed the 7.6 release profile to skip javadocs by default. > JavaDocs for Teiid needs to contain only what's exposed. > -------------------------------------------------------- > > Key: TEIID-1752 > URL: https://issues.jboss.org/browse/TEIID-1752 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 7.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.4.1 > > > Make adjustments to the pom.xml to exclude packages that don't need to be javadoc'd. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1828) Dependent critiera in query plan but missing in actual query and additional information is provided

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1828?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1828. ----------------------------------- Resolution: Done Added the max ndv values to the intermediate plan and a warning log indicating when the dependent join is not performed. A possible further enhancement would be to add the max ndv values to the final plan as well. > Dependent critiera in query plan but missing in actual query and additional information is provided > --------------------------------------------------------------------------------------------------- > > Key: TEIID-1828 > URL: https://issues.jboss.org/browse/TEIID-1828 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.4.1 > Environment: Oracle datasource, but likely all > Reporter: Tom Fonteyne > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.6 > > > tested on EDS 5.2 ER3 and ER6, same results: > We're running a query which has two sets of dependent criteria in one of the queries. The plan looks ok, and in the command log we see that EDS is getting both sets of dependent criteria and bringing back rows which we would expect to be passed into the final query. > The problem is that the final query has 1=1 in the place of where the dependent criteria should be. > In the plan: > + Query:SELECT g_0.account_code AS c_0, g_0.book_code AS c_1, SUM(g_0.func_amount) AS c_2 FROM TSL_SQL_Source.TSL.TSL_FINANCIAL_ACCOUNT_ITEMS_T2 AS g_0 WHERE (g_0.business_date = {d'2011-06-29'}) AND (g_0.account_code IN (<dependent values>)) AND (g_0.book_code IN (<dependent values>)) GROUP BY g_0.account_code, g_0.book_code ORDER BY c_0 NULLS FIRST > The source specific query from the command log: > 2011-11-14 11:35:35,313 DEBUG [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue60) Source-specific command: SELECT g_0.ACCOUNT_CODE AS c_0, g_0.BOOK_CODE AS c_1, SUM(g_0.FUNC_AMOUNT) AS c_2 FROM TSL_FINANCIAL_ACCOUNT_ITEMS_T2 g_0 WHERE g_0.BUSINESS_DATE = {d '2011-06-29'} AND 1 = 1 AND 1 = 1 GROUP BY g_0.ACCOUNT_CODE, g_0.BOOK_CODE ORDER BY c_0 NULLS FIRST > Stats should be correct in the VDB. We also updated the stats using the system procedures just before executing the query. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1831) Perl client using DBD:Pg hangs with resultset > 512 rows

by Van Halbert (Created) (JIRA)

Perl client using DBD:Pg hangs with resultset > 512 rows -------------------------------------------------------- Key: TEIID-1831 URL: https://issues.jboss.org/browse/TEIID-1831 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.4.1 Environment: java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.23.1.9.10.el5_7-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) on Red Hat Enterprise Linux Server release 5.7 (Tikanga) Teiid 7.5 with a patch applied for issue TEIID-1812 Perl client running on either Fedora 16 or RHEL 5.7 Using perl-DBD-Pg-2.18.0-3.fc16.x86_64 Reporter: Graeme Gillies Assignee: Steven Hawkins Fix For: 7.6 We are using a simple perl script to connect to teiid and run a query, spitting out the results. Unfortunately we find that the perl client hangs forever when trying to execture/return a resultset > 512 rows, but 512 or less it runs fine The code for a test script is as follows {code} #! /usr/bin/perl use strict; use warnings; use DBI; my $db_type = 'Pg'; my $db_name = 'EngVDBF'; my $db_host = 'vdb.engineering.redhat.com'; my $db_port = 35432; my $user = 'teiid'; my $pass = 'teiid'; my $attr = { AutoCommit => 0, RaiseError => 1 }; my $dsn = sprintf( "dbi:%s:dbname=%s;host=%s;port=%s", $db_type, $db_name, $db_host, $db_port ); my $dbh = DBI->connect( $dsn, $user, $pass, $attr ); my $limit = ( $ARGV[0] ) ? "limit $ARGV[0]" : ""; my $query = <<QUERY; select bugs.bug_id, bugs.priority, bugs.bug_severity from BugzillaS.bugs bugs $limit QUERY my $sth = $dbh->prepare($query); $sth->execute(); while ( my @row = $sth->fetchrow_array() ) { print join( ',', map {"\"$_\""} @row ) . "\n"; } $sth->finish(); $dbh->disconnect(); {code} When running {noformat} ./teiid.pl 512 {noformat} Query runs fine, when we run {noformat} ./teiid.pl 513 {noformat} Client just sits there forever (the query actually has about 1800 odd rows returning). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-245) Update costing metadata at runtime

by Steven Hawkins (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIID-245?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-245: -------------------------------------- Another more pervasive approach to consider would be stream sampling based upon query results. See also http://wiki.postgresql.org/wiki/Estimating_Distinct for a good overview. However with metadata updates being non-persistent by default and possible performance issues with initial queries that would be a lower priority solution than simply being able to import source system statistics. > Update costing metadata at runtime > ---------------------------------- > > Key: TEIID-245 > URL: https://issues.jboss.org/browse/TEIID-245 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Attachments: OracleExecutionFactory.java.patch > > > Defect Tracker #24584: Cost analysis should be both a design-time activity and scheduled/feed during runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011