The Datastore MySQL import submodule handles an empty file incorrect (differently than the import via CSV parser) resulting in an error during execution of the import:
ValueError: fread(): Argument #2 ($length) must be greater than 0 in fread()
This will lead to termination of the import job, while compared with the import via CSV parser (without Datastore MySQL import module) the import job will continue and just mark the empty file with an error in the import status.
Expected Behavior
Datastore MySQL import should show the same behavior on import of an empty file as the import via CSV parser (mark the file as an error in import status, but not terminate the whole import job).
Steps To Reproduce
Upload an empty CSV file to a distribution
Start the import to the datastore (via cron)
Note the error message starting with "Error importing resource id ..."
Compare this to:
Upload an empty CSV file to a distribution
enable the datastore_mysql_import submodule
Start the import to the datastore (via cron)
Note the different error message and note that cron execution is terminated
Current Behavior
The Datastore MySQL import submodule handles an empty file incorrect (differently than the import via CSV parser) resulting in an error during execution of the import:
ValueError: fread(): Argument #2 ($length) must be greater than 0 in fread()This will lead to termination of the import job, while compared with the import via CSV parser (without Datastore MySQL import module) the import job will continue and just mark the empty file with an error in the import status.
Expected Behavior
Datastore MySQL import should show the same behavior on import of an empty file as the import via CSV parser (mark the file as an error in import status, but not terminate the whole import job).
Steps To Reproduce
Compare this to:
Relevant log output (optional)
No response
Anything else?
No response