[MXS-3302] LDI fails when Table has Data Type TEXT Created: 2020-11-18 Updated: 2021-05-02 Resolved: 2020-12-29 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | markus makela |
| Resolution: | Cannot Reproduce | Votes: | 1 |
| Labels: | need_feedback | ||
| Sprint: | MXS-SPRINT-121 |
| Description |
|
From Customer testing MaxScale 10.5.6 and the campaigns table still failed to load. I looked at the columnstore logs and it looked like it imported 0 rows, but it failed somewhere. Couldn't tell where. |
| Comments |
| Comment by markus makela [ 2020-11-24 ] | ||||
|
Does this happen when going past MaxScale directly to the database? MaxScale processes the load identically in both cases. In addition, is this LOAD DATA INFILE or LOAD DATA LOCAL INFILE? The former is processed by the database and MaxScale just routes the query to the current master. Please also update the issue with what version of MaxScale this happens with. | ||||
| Comment by David Hill (Inactive) [ 2020-12-01 ] | ||||
|
Using the 2.5.5 release of Maxscale. | ||||
| Comment by markus makela [ 2020-12-07 ] | ||||
| ||||
| Comment by David Hill (Inactive) [ 2020-12-08 ] | ||||
|
1. Here is my test setup. 1 maxscale server over 1 columnstore server. This is just to test this issue.
--------------
-------------- 3. Successfully ran cpimport and LDI from the Columnstore server. 4. Issue reported is its not working when its sent through maxscale server, a table with text data type. So my setup I guess isnt right and could use some help. I didn't located anything in the Docs about how to setup and send sql statments through maxscale. | ||||
| Comment by markus makela [ 2020-12-28 ] | ||||
|
Does this happen with the latest ColumnStore from 10.5? I tried to reproduce this but I ran into a problem where it crashes with a currently unknown bug. | ||||
| Comment by markus makela [ 2020-12-29 ] | ||||
|
I cannot reproduce this with the latest MaxScale and ColumnStore releases and since there was a bug that affected older ColumnStore versions, it's likely that this isn't a MaxScale bug. Until we can find a way to reproduce this with the latest versions, I'll resolve this as Cannot Reproduce. |