[MCOL-1025] When source table does not exist or is empty in Master database, adapter gives incorrect error Created: 2017-11-10  Updated: 2023-10-26  Resolved: 2018-01-10

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.1.1
Fix Version/s: 1.1.0

Type: Bug Priority: Minor
Reporter: Dipti Joshi (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

Table t3 does not exist in test database on master - the error given is Failed to read row. Instead of it should say "Table does not exist on master"

./mxs_adapter -h 172.21.0.7 -P 4001 -u cdcuser -p cdc -r 5 -n test t3
 
Failed to read row: Request timed out

Same happens if Table t3 exists on master , but is empty with no rows. - In this case there should not be an error due to master side.

 Comments   
Comment by markus makela [ 2017-11-10 ]

The error message has been fixed in 70b01f0555e70872a607f18678976c6c42463a6a. Due to the fact that MaxScale only creates the table when the first row is received, there's currently no way to know the difference between an empty table an a table that does not exist.

The fixed error message

 
[markusjm@localhost build]$ ./mxs_adapter -c Columnstore.xml -umaxuser -pmaxpwd -h $maxscale_IP -P 4001 -n -r 5 test t5
 
MaxScale connection could not be created: MaxScale responded with an error: ERR NO-FILE File 'test.t5.000001.avro' not found.

Generated at Thu Feb 08 02:25:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.