Skip to content

[UI] Fix virtual update not applied and rename 'logical' to 'virtual'#579

Merged
mykalmax merged 5 commits intomainfrom
max/UI_fix_virtual_update_not_applied
Mar 22, 2023
Merged

[UI] Fix virtual update not applied and rename 'logical' to 'virtual'#579
mykalmax merged 5 commits intomainfrom
max/UI_fix_virtual_update_not_applied

Conversation

@mykalmax
Copy link
Contributor

No description provided.

@mykalmax mykalmax requested a review from vchan March 22, 2023 00:22
'All changes and their downstream dependencies can be fully previewed before they get promoted. If during plan creation no data gaps have been detected and only references to new model versions need to be updated, then such update is referred to as logical. Logical updates impose no additional runtime overhead or cost.',
hasVirtualUpdate: false,
virtualUpdateDescription:
'All changes and their downstream dependencies can be fully previewed before they get promoted. If during plan creation no data gaps have been detected and only references to new model versions need to be updated, then such update is referred to as Virtual. Virtual updates impose no additional runtime overhead or cost.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then such update is referred to as Virtual Update. Virtual Updates

The feature is "Virtual Update" and I always uppercase the update.

)

const hasLogicalUpdate = hasChanges && isFalse(hasBackfills)
// const hasVirtualUpdate = hasChanges && isFalse(hasBackfills)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// const hasVirtualUpdate = hasChanges && isFalse(hasBackfills)

'All changes and their downstream dependencies can be fully previewed before they get promoted. If during plan creation no data gaps have been detected and only references to new model versions need to be updated, then such update is referred to as logical. Logical updates impose no additional runtime overhead or cost.',
hasVirtualUpdate: false,
virtualUpdateDescription:
'All changes and their downstream dependencies can be fully previewed before they get promoted. If during plan creation no data gaps have been detected and only references to new model versions need to be updated, then such update is referred to as Virtual Update. Virtual Updates impose no additional runtime overhead or cost.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'All changes and their downstream dependencies can be fully previewed before they get promoted. If during plan creation no data gaps have been detected and only references to new model versions need to be updated, then such update is referred to as Virtual Update. Virtual Updates impose no additional runtime overhead or cost.',
'All changes and their downstream dependencies can be fully previewed before they get promoted. If during plan creation no data gaps have been detected and only references to new model versions need to be updated, then such an update is referred to as a Virtual Update. Virtual Updates impose no additional runtime overhead or cost.',

await request.app.state.task

return models.ApplyResponse(type="backfill" if plan.requires_backfill else "logical")
return models.ApplyResponse(type="backfill" if plan.requires_backfill else "virtual")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use the ApplyType enum here.

Co-authored-by: Vincent Chan <vchan@users.noreply.github.com>
@mykalmax mykalmax merged commit b1dba79 into main Mar 22, 2023
@mykalmax mykalmax deleted the max/UI_fix_virtual_update_not_applied branch March 22, 2023 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants