-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Labels
area/bulk-loaderIssues related to bulk loading.Issues related to bulk loading.area/import-exportIssues related to data import and export.Issues related to data import and export.area/operationsRelated to operational aspects of the DB, including signals, flags, env vars, etc.Related to operational aspects of the DB, including signals, flags, env vars, etc.area/usabilityIssues with usability and error messagesIssues with usability and error messagesstatus/acceptedWe accept to investigate/work on it.We accept to investigate/work on it.
Description
Observed:
When importing some RDF data sets given to us by a third-party we have encountered a few schema issues whereby the bulk loader (which we are running in a Docker container) reports the (legit) error and fails. It was not immediately obvious simply by looking at the log whether or not the process stopped there or continued; we tend to let these imports run overnight and the first thing we do is view the log in the morning.
Expected result:
The bulk loader should explicitly state in the log whether or not it completed processing the data set; especially where in the data set it stopped. Some kind of "Exiting" message would be the least optimal solution but still better than nothing.
Metadata
Metadata
Assignees
Labels
area/bulk-loaderIssues related to bulk loading.Issues related to bulk loading.area/import-exportIssues related to data import and export.Issues related to data import and export.area/operationsRelated to operational aspects of the DB, including signals, flags, env vars, etc.Related to operational aspects of the DB, including signals, flags, env vars, etc.area/usabilityIssues with usability and error messagesIssues with usability and error messagesstatus/acceptedWe accept to investigate/work on it.We accept to investigate/work on it.