[MCOL-3734] 'insert into table select' syntax not working in 1.4.2 Created: 2020-01-20 Updated: 2020-08-25 Resolved: 2020-01-22 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | writeengine |
| Affects Version/s: | 1.4.2 |
| Fix Version/s: | 1.4.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Patrick LeBlanc (Inactive) |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2020-1 |
| Description |
|
Reported by customer.. Is there a plan to re-implement the 'insert into table select' syntax with the newest release of Columnstore? We utilized this quite often with Columnstore tables in the 1.2.5 and earlier versions. SQL statement will be in the followup comments with Eng only permissions MariaDB [assay_archive]> insert into .... Select Handler lacks support for some vtable features, including: nothing in the error logs, this in the debug log Where the query returned to check the err.log, the log is actually completely empty and the debug.log just states that there is an error. Jan 20 10:34:35 mdb-cs2 dbcon[578022]: 35.694801 |34|0|0| D 24 CAL0001: Start SQL statement: insert into beef_batch_col_1 select * from beef_batch_2; |assay_archive| |
| Comments |
| Comment by David Hill (Inactive) [ 2020-01-21 ] |
|
from customer I suppose that is possible with our testing. The shutdown and restart alone did not change anything. As well as the recommended commands. I cleaned the system completely and restarted with a combined 2 PM set-up with S3 storage and the insert into select worked as expected.. so still trying to see why it did not work I tried a few configurations and it is completely possible that these are not expected to work anymore as they did previously: Successful for the insert into select postConfigure: Failed for insert into select with previous errors after postConfigure: I understand that the way things will be configured going forward will be changed.. but it appears this works on one configuration and not on another right now. |
| Comment by Patrick LeBlanc (Inactive) [ 2020-01-22 ] |
|
Other tickets currently being worked on will make sure the user runs post-install, which would fix this problem. Other follow-on work may include a better error message and better logging to lead the user to the sol'n. In this case, cpimport returned an error code, and there is no info in the log files to point us to the fact that some dirs were missing. |