Skip to content

Add bulk_import_export_batches & bulk_import_batch_trackers db tables

What does this MR do and why?

This MR makes changes to bulk_import_* database tables to lay foundation for performing GitLab Direct Transfer (aka GitLab Migration)

  • Add bulk_import_export_batches db table
    • Used to keep track of state of relation export of a batch (belongs to BulkImports::Export)
  • Add bulk_import_batch_trackers db table
    • Used to keep track of state of relation import of a batch (belongs to BulkImports::Tracker)
  • Add 3 new columns to bulk_import_exports db table
    • batched - to indicate if export is performed in batches. Defaults to fals
    • batches_count - to indicate the total number of batches exported
    • total_objects_count - to indicate how many objects (rows) were exported
  • Add 1 new column to bulk_import_export_uploads db table
    • batch_id - to assicate BulkImport::ExportUpload with an export batch (in the future MR)
  • Add 1 new column to bulk_import_trackers db table
    • batched - to indicate the the import should be performed in batches

Mentions #391219 (closed)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports