Bug #102730 ndb_import fails to load CSV files created by DBT2
Submitted: 25 Feb 2021 3:43 Modified: 3 Feb 2022 15:40
Reporter: Mikael Ronström Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious)
Version:8.0.23 OS:Any
Assigned to: CPU Architecture:Any

[25 Feb 2021 3:43] Mikael Ronström 
Description:
DBT2 generates no column for AUTO_INCREMENT columns.
This is acceptable by MySQL LOAD DATA INFILE, it is
not acceptable by ndb_import that fails with too few
columns. Haven't tested if one can replace the empty
column by a NULL indicator.

How to repeat:
Load CSV from history table in DBT2.

Suggested fix:
Make ndb_import able to handle same things that
LOAD DATA INFILE can handle.
[25 Feb 2021 7:54] MySQL Verification Team 
Hello Mikael,

Thank you for the report and feedback.

Sincerely,
Umesh
[3 Feb 2022 15:40] Jon Stephens 
Documented fix as follows in the NDB 8.0.30 changelog:

    A new --missing-ai-column option is added to ndb_import. This
    enables ndb_import to accept a CSV file from which the data for
    an AUTO_INCREMENT column is missing and to supply these values
    itself, much as LOAD DATA does.

    This option works only when importing a single table with
    ndb_import.

Also added the new option to the 8.0 Manual.

Closed.