[MDEV-14803] connect.pivot failed in buildbot with "failed to discover table" Created: 2017-12-29  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect, Tests
Affects Version/s: 10.1, 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Olivier Bertrand
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/bld-starfs-debug/builds/609/steps/test_1/logs/stdio
(with ps protocol)

connect.pivot                            w2 [ fail ]
        Test ended at 2017-12-14 16:24:07
 
CURRENT_TEST: connect.pivot
mysqltest: At line 158: query 'CREATE TABLE fruit_pivot ENGINE=CONNECT TABLE_TYPE=pivot TABNAME=fruit' failed: 1939: Engine CONNECT failed to discover table `test`.`fruit_pivot` with 'CREATE TABLE whatever (`id` INT(10) UNSIGNED NOT NULL,`                        7bfff520` INT(11) FLAG=1,`                        7bfff520` INT(11) FLAG=1,`                        7bfff520` INT(11) FLAG=1,`                        7bfff520` INT(11) FLAG=1) TABLE_TYPE='pivot' TABNAME='fruit''
 
The result from queries just before the failure was:
< snip >
 
DROP TABLE pivet;
DROP TABLE pets;
#
# MDEV-5734
#
CREATE TABLE fruit (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(32) NOT NULL,
`cnt` int(11) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;
INSERT INTO fruit VALUES (1,'apple',1),(2,'banana',1),(3,'apple',2),(4,'cherry',4),(5,'durazno',2);
SELECT * FROM fruit;
id	name	cnt
1	apple	1
2	banana	1
3	apple	2
4	cherry	4
5	durazno	2
CREATE TABLE fruit_pivot ENGINE=CONNECT TABLE_TYPE=pivot TABNAME=fruit;



 Comments   
Comment by Elena Stepanova [ 2018-02-04 ]

10.1:
http://buildbot.askmonty.org/buildbot/builders/bld-starfs-debug/builds/755/steps/test_1/logs/stdio

Comment by Olivier Bertrand [ 2018-02-04 ]

This is very strange. Firstly because it apparently never happened so far, secondly because it was successful when retried.
I could not reproduce it on Windows, on which platform did this occur?
Debugging it, the column names (that were wrongly set as 7bfff520 when it failed) are retrieved from a query sent to MariaDB. Therefore, the bug can be in CONNECT code but also possibly in MariaDB code.
This can be fixed only by debugging this on the platform where it occured... and if it still occur when debugging!
Right now, I can't do much about it.

Generated at Thu Feb 08 08:16:24 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.