August 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2612) Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2612?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2612. ----------------------------------- Resolution: Done This was not noticed initially as the pg jdbc driver essentially drops the portal suspend result - however that is not expected when the max rows is given as 0, so the DBD-Pg is basically correct in making the assumption that it will not get that response back. Corrected the response, switched to non-blocking cursor move, and added a couple of hacks to test the cursor logic through the pg jdbc driver. > Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken > ------------------------------------------------------------------ > > Key: TEIID-2612 > URL: https://issues.jboss.org/browse/TEIID-2612 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.5 > Reporter: Graeme Gillies > Assignee: Steven Hawkins > Fix For: 8.5 > > > Hi, > We are testing the git head of teiid 8.5 in JBoss EAP 6.1, running with java 7, and are attempting to connect to teiid using perl-DBD-Pg. > We have a code snippet that looks like > {noformat} > #! /usr/bin/perl > use strict; > use warnings; > use DBI; > my $db_type = 'Pg'; > my $db_name = 'TestZipVDB'; > my $db_host = 'teiid.host'; > my $db_port = 5432; > my $user = 'teiid'; > my $pass = 'teiid'; > my $attr = { AutoCommit => 0, RaiseError => 1 }; > my $dsn = sprintf( "dbi:%s:dbname=%s;host=%s;port=%s;sslmode=prefer", > $db_type, $db_name, $db_host, $db_port ); > my $dbh = DBI->connect( $dsn, $user, $pass, $attr ); > my $query = <<QUERY; > select count(1) from bugzilla.bugs > QUERY > my $sth = $dbh->prepare($query); > $sth->execute(); > while ( my @row = $sth->fetchrow_array() ) { > print join( ',', map {"\"$_\""} @row ) . "\n"; > } > $sth->finish(); > $dbh->disconnect(); > {noformat} > However when running this with ssl turned on or off we get the following error > {noformat} > DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. > DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. > Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db handle dbname=TestZipVDB;host=teiid.host;port=5432 at ./a.pl line 25. > {noformat} > It seems that ODBC/Pg Compatibility was broken with a recent commit? > We git this error on a RHEL-6 box running postgresql 8.4 and on Fedora 19 running postgresql 9.2 > Regards, > Graeme -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2612) Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2612?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2612: ---------------------------------- Fix Version/s: 8.5 Component/s: ODBC This is a regression from TEIID-2610. We are reusing the send cursor result now for regular results, which was sending back a portal suspended even if all rows were fetched. > Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken > ------------------------------------------------------------------ > > Key: TEIID-2612 > URL: https://issues.jboss.org/browse/TEIID-2612 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.5 > Reporter: Graeme Gillies > Assignee: Steven Hawkins > Fix For: 8.5 > > > Hi, > We are testing the git head of teiid 8.5 in JBoss EAP 6.1, running with java 7, and are attempting to connect to teiid using perl-DBD-Pg. > We have a code snippet that looks like > {noformat} > #! /usr/bin/perl > use strict; > use warnings; > use DBI; > my $db_type = 'Pg'; > my $db_name = 'TestZipVDB'; > my $db_host = 'teiid.host'; > my $db_port = 5432; > my $user = 'teiid'; > my $pass = 'teiid'; > my $attr = { AutoCommit => 0, RaiseError => 1 }; > my $dsn = sprintf( "dbi:%s:dbname=%s;host=%s;port=%s;sslmode=prefer", > $db_type, $db_name, $db_host, $db_port ); > my $dbh = DBI->connect( $dsn, $user, $pass, $attr ); > my $query = <<QUERY; > select count(1) from bugzilla.bugs > QUERY > my $sth = $dbh->prepare($query); > $sth->execute(); > while ( my @row = $sth->fetchrow_array() ) { > print join( ',', map {"\"$_\""} @row ) . "\n"; > } > $sth->finish(); > $dbh->disconnect(); > {noformat} > However when running this with ssl turned on or off we get the following error > {noformat} > DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. > DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. > Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db handle dbname=TestZipVDB;host=teiid.host;port=5432 at ./a.pl line 25. > {noformat} > It seems that ODBC/Pg Compatibility was broken with a recent commit? > We git this error on a RHEL-6 box running postgresql 8.4 and on Fedora 19 running postgresql 9.2 > Regards, > Graeme -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2612) Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken

by Graeme Gillies (JIRA)

Graeme Gillies created TEIID-2612: ------------------------------------- Summary: Teiid ODBC compatibility with perl-DBD-Pg for postgresql is broken Key: TEIID-2612 URL: https://issues.jboss.org/browse/TEIID-2612 Project: Teiid Issue Type: Bug Affects Versions: 8.5 Reporter: Graeme Gillies Assignee: Steven Hawkins Hi, We are testing the git head of teiid 8.5 in JBoss EAP 6.1, running with java 7, and are attempting to connect to teiid using perl-DBD-Pg. We have a code snippet that looks like {noformat} #! /usr/bin/perl use strict; use warnings; use DBI; my $db_type = 'Pg'; my $db_name = 'TestZipVDB'; my $db_host = 'teiid.host'; my $db_port = 5432; my $user = 'teiid'; my $pass = 'teiid'; my $attr = { AutoCommit => 0, RaiseError => 1 }; my $dsn = sprintf( "dbi:%s:dbname=%s;host=%s;port=%s;sslmode=prefer", $db_type, $db_name, $db_host, $db_port ); my $dbh = DBI->connect( $dsn, $user, $pass, $attr ); my $query = <<QUERY; select count(1) from bugzilla.bugs QUERY my $sth = $dbh->prepare($query); $sth->execute(); while ( my @row = $sth->fetchrow_array() ) { print join( ',', map {"\"$_\""} @row ) . "\n"; } $sth->finish(); $dbh->disconnect(); {noformat} However when running this with ssl turned on or off we get the following error {noformat} DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. DBD::Pg::st execute failed: unexpected response from server; first received character was "s" at ./a.pl line 25. Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db handle dbname=TestZipVDB;host=teiid.host;port=5432 at ./a.pl line 25. {noformat} It seems that ODBC/Pg Compatibility was broken with a recent commit? We git this error on a RHEL-6 box running postgresql 8.4 and on Fedora 19 running postgresql 9.2 Regards, Graeme -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2611) Client forwards compatibility issue

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2611?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2611: --------------------------------- Fix Version/s: 7.7.8 > Client forwards compatibility issue > ----------------------------------- > > Key: TEIID-2611 > URL: https://issues.jboss.org/browse/TEIID-2611 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 8.4, 7.7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5, 7.7.8 > > > TEIID-2504 introduced a regression such that 8.3 and older clients against a 8.4+ or 7.7.7+ servers will throw an exception when doing a multi-batch query. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2611) Client forwards compatibility issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2611?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2611: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=991160 > Client forwards compatibility issue > ----------------------------------- > > Key: TEIID-2611 > URL: https://issues.jboss.org/browse/TEIID-2611 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 8.4, 7.7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > TEIID-2504 introduced a regression such that 8.3 and older clients against a 8.4+ or 7.7.7+ servers will throw an exception when doing a multi-batch query. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2604) ODBC string error response message is incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2604?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2604: --------------------------------- Fix Version/s: 7.7.8 > ODBC string error response message is incorrect > ----------------------------------------------- > > Key: TEIID-2604 > URL: https://issues.jboss.org/browse/TEIID-2604 > Project: Teiid > Issue Type: Enhancement > Components: ODBC > Affects Versions: 7.1.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5, 7.7.8 > > > The null termination character is missing from the error response message options. This is typically only thrown for internal/protocol errors. Clients may not behave as expected to this response. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2495) Detect situations in which intermediate updates are not needed such that the updates can be grouped

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2495?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2495: ---------------------------------- Fix Version/s: 8.5 Will take an initial pass at this in 8.5. The scenarios are: - A single update statement as the trigger - here we can convert it to a bulk operation - A series of update statements - which can at least be converted to a batched update - something more complex such that the updates can be grouped/delayed I'll at least get something in for the simple single update case. > Detect situations in which intermediate updates are not needed such that the updates can be grouped > --------------------------------------------------------------------------------------------------- > > Key: TEIID-2495 > URL: https://issues.jboss.org/browse/TEIID-2495 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.3 > Reporter: Jing Li > Assignee: Steven Hawkins > Fix For: 8.5 > > > The default processing model is to simply perform the execution for each row, an enhancment would be required for Teiid to detect situations in which intermediate updates are not needed such that the updates can be grouped. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2611) Client forwards compatibility issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2611?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2611. ----------------------------------- Resolution: Done Made the setting of the delayserialization parameter more straightforward and also expanded its applicability to scrollable results. > Client forwards compatibility issue > ----------------------------------- > > Key: TEIID-2611 > URL: https://issues.jboss.org/browse/TEIID-2611 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 8.4, 7.7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > TEIID-2504 introduced a regression such that 8.3 and older clients against a 8.4+ or 7.7.7+ servers will throw an exception when doing a multi-batch query. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2591) Incorrect values returned from system table on dependent side of join

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2591?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2591: --------------------------------- Fix Version/s: 7.7.8 > Incorrect values returned from system table on dependent side of join > --------------------------------------------------------------------- > > Key: TEIID-2591 > URL: https://issues.jboss.org/browse/TEIID-2591 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5, 7.7.8 > > > If a system table is marked as the dependent side of a join (should be rarely planned, but can be forced with a makedep) the system table access is not corrected for the projection and may return values that are not matched to the columns requested. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2611) Client forwards compatibility issue

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2611: ------------------------------------- Summary: Client forwards compatibility issue Key: TEIID-2611 URL: https://issues.jboss.org/browse/TEIID-2611 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.7.7, 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 TEIID-2504 introduced a regression such that 8.3 and older clients against a 8.4+ or 7.7.7+ servers will throw an exception when doing a multi-batch query. -- 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, 5 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