[MXS-1160] Load infile not working on Schemarouter Created: 2017-03-03  Updated: 2017-03-31  Resolved: 2017-03-31

Status: Closed
Project: MariaDB MaxScale
Component/s: schemarouter
Affects Version/s: 2.0.1, 2.0.4, 2.1.0
Fix Version/s: 2.2.0

Type: Bug Priority: Minor
Reporter: Marcelo Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Linux 2.6.32-642.6.2.el6.x86_64, CentOS release 6.8 (Final)

Issue Links:
Relates
relates to MXS-365 Load data local infile connection abo... Closed
Sprint: 2017-30, 2017-31

 Description   

Load Infile is not working when used with SchemaRouter. ERROR 2013 (HY000): Lost connection to MySQL server during query

On MaxScale log, we see the following:

2017-03-03 09:32:15 error : [qc_sqlite] The query could not be parsed. Response not valid.
2017-03-03 09:32:15 error : [qc_sqlite] The provided buffer does not contain a COM_QUERY, but a UNKNOWN MYSQL PA
CKET TYPE. (subsequent similar messages suppressed for 10000 milliseconds)
2017-03-03 09:32:15 error : [qc_sqlite] The query could not be parsed. Response not valid. (subsequent similar m
essages suppressed for 10000 milliseconds)
2017-03-03 09:32:15 error : [schemarouter] Failed to execute

Works perfectly when the same operation is used with ReadWriteSplit router.

It seems similar to MXS-365 (https://mariadb.atlassian.net/browse/MXS-365)

 Comments   
Comment by markus makela [ 2017-03-07 ]

The code to handle LOAD DATA LOCAL INFILE doesn't seem to exist in the schemarouter. It seems very likely that the cause is the same as in MXS-365.

Comment by markus makela [ 2017-03-31 ]

Added support for LOAD DATA LOCAL INFILE.

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