Page MenuHomePhorge

Data migration tool
ClosedPublic

Authored by machniak on Jul 1 2024, 11:31 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 3, 1:07 PM
Unknown Object (File)
Sat, Nov 2, 9:12 PM
Unknown Object (File)
Mon, Oct 28, 4:04 PM
Unknown Object (File)
Sun, Oct 27, 2:35 PM
Unknown Object (File)
Sat, Oct 19, 5:40 AM
Unknown Object (File)
Wed, Oct 16, 3:28 PM
Unknown Object (File)
Mon, Oct 7, 7:31 PM
Unknown Object (File)
Sep 20 2024, 11:18 AM
Subscribers
Restricted Project

Details

Reviewers
mollekopf
Group Reviewers
Restricted Project
Commits
rKfd6cc6b72094: Data migration tool
Summary

With basic data migration from Exchange

Test Plan

TODO

Diff Detail

Repository
rK kolab
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

machniak created this revision.
mollekopf subscribed.

I think we can merge it and take it from there.

src/app/DataMigrator/Engine.php
133

If the fetch itemItemList implementation wouldn't dispatch a job via callback, then it could customize if a per-item job is spawned or not.
The counting could e.g. be handled by a Engine::dispatchJob implementation that is called by the exporter.

This revision is now accepted and ready to land.Jul 1 2024, 12:09 PM
src/app/DataMigrator/Engine.php
133

I was thinking about a separate method that could be implemented optionally by an exporter. Then we could have another job MultiItemJob. Then an importer would also optionally have another method to import multiple items in one go.

This revision was automatically updated to reflect the committed changes.