-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loader - v3 to v4 data migration #368
Comments
@amhudson @gchickma I have started the analysis on the data migration required. See above. My plan is to focus energy on Task Templates, Workflows, Workflow Revisions, and collection name changes. Currently no plan to do task activity (now task runs) and in two minds on workflow activity (now workflow runs). -- I don't believe the historical activity not being available is the worst thing. What are your thoughts on whether we bother, or if we just proceed with a partial (minimal subset of fields to make it show up as a workflow_run and not render the detail) |
Added support for Azure Cosmos DB API for MongoDB |
Separated out v4 changes into separate class and changeset numbers |
Added Team Changes |
Need to update all this and move to the Architecture docs |
Flow v3 to v4 Model Changes
As part of v3 to v4, a data migration exercise is needed for the collections.
Task Templates
task_templates
Map<String, String>
Map<String, Object>
Task Template Spec
Workflows
workflows
List<KeyValuePair>
toMap<String, String>
workflow_revisions
workflow_revisions
Triggers
Workflow Revisions
workflow_revisions
(previouslyworkflows_revisions
)workflows
(not the revision) - model also changedworkflows
(not the revision) - model also changedWorkspaces
V3
V4
Tasks
boomerang.io/position
Dependencies
boomerang.io/points
Config
boomerang.io/nodeId
.Workflow Runs
workflow_runs
(previouslyworkflows_activity
)Map<String, String>
initiatedByRef
initiatedByRef
Task Runs
task_runs
(previously:workflows_activity_task
)workflow_revision
workflow_revision
Task Locks
locks
(previously:tasks_locks
)Model is the same, however have introduced support for Azure CosmosDB API for MongoDB which means the TTL and indexes are slightly different depending on MongoDB implementation.
Actions
actions
(previously:workflows_activity_approval
)Teams
teams
List<KeyValuePair>
toMap<String, String>
approver_groups
ApproverGroups
approver_groups
Relationship
relationships
Supporting Models
RunStatus
TeamStatus
The text was updated successfully, but these errors were encountered: