[MDEV-15397] CONNECT engine JDBC error messages need more info Created: 2018-02-23  Updated: 2018-03-05

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.1.29
Fix Version/s: 10.1

Type: Bug Priority: Major
Reporter: Robert Dyas Assignee: Olivier Bertrand
Resolution: Unresolved Votes: 0
Labels: None
Environment:

CentOS7


 Description   

When something goes wrong with the execution of a CONNECT JDBC statement (typically a SELECT) the error message doesn't contain enough information. A typical error message would be as follows:

Got error 174 'Cannot get result size rc=-1' from CONNECT)

The remote database is likely returning a detailed error message, and this should be passed along into the connect error message... maybe something like:

Got error 174 'Cannot get result size rc=-1 (Table Custumers does not exist)' from CONNECT)

i.e. just nest the message. This is hopefully very easy by calling exception.getLocalizedMessage() on any exception thrown from JDBC and passing the returned text along in error messages.

 Comments   
Comment by Olivier Bertrand [ 2018-03-05 ]

Not sure this comes only from CONNECT. For instance:

CREATE TABLE testerr (
 
id INT NOT NULL,
 
msg CHAR(32))
 
ENGINE=CONNECT TABLE_TYPE=JDBC TABNAME=nonexist 
CONNECTION='jdbc:mysql://localhost/test?user=root&useSSL=false';
 
select * from testerr;

Replies:

1296: Got error 174 'ExecuteQuery:
 
com.mysql.jdbcc4.MySQLSyntaxErrorException:
 
Table 'test.nonexist' doesn't exist' from CONNECT

CONNECT cannot do more than adding the message returned by the JDBC driver.

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