[MCOL-3717] cpimport fails intermittently with "invalid default value in system catalog" Created: 2020-01-09 Updated: 2023-10-25 Resolved: 2023-10-25 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | cpimport |
| Affects Version/s: | 1.4.1 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | Faisal Saeed (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
RHEL 7 Linux with 48 cores 6TB SSD storage |
||
| Description |
|
When loading a text data file I faced this issue intermittently that says a particular timestamp column has an invalid default value in the system catalog.
The column is defined as `ISSUE_DATE timestamp(6) NOT NULL` Rerunning the same cpimport script a second or a third-time always works successfully. |
| Comments |
| Comment by David Hall (Inactive) [ 2020-01-09 ] | |||||||||||
|
Please show the results of running: The normal default is "current_timestamp() ON UPDATE current_timestamp()", but if somehow something else got in there, we need to know. Also if your import file has values for the timestamp, rather than letting the default handle it, that may be a clue, especially if that value is "0000-00-00 00:00:00" or some variation of 0. | |||||||||||
| Comment by Ryan Wallace [ 2020-07-26 ] | |||||||||||
|
I'm also experiencing a similar intermittent error using cpimport with the command:
Intermittently, the command returns the following error:
show create table scheduled_and_hours_worked_daily returns the following entry for job_archived_date:
select defaultvalue from calpontsys.syscolumn where columnname='job_archived_date'; returns
(A column with the same name appears in 4 tables.) Like for Fasial, rerunning the same command a second, third, or fourth time, cpimport always succeeds. |