Skip to content
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

applying a plan should use the refreshed state #15421

Closed
wants to merge 2 commits into from

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Jun 28, 2017

When applying a plan, a copy of the plan's state is initially persisted
to state storage, which may in turn increment the serial number. The
apply operation stil uses the state stored in the plan, which may have a
lower serial number.

Now we no longer use the plan state when building the apply context, but
still perform a sanity check to ensure that the state be used is
equivalent.

TODO: test case

@jbardin jbardin requested a review from apparentlymart June 28, 2017 22:29
@apparentlymart apparentlymart force-pushed the jbardin/apply-plan-state branch 2 times, most recently from 98b48a0 to 67c6a53 Compare June 28, 2017 23:42
When applying a plan, a copy of the plan's state is initially persisted
to state storage, which may in turn increment the serial number. The
apply operation stil uses the state stored in the plan, which may have a
lower serial number.

Now we no longer use the plan state when building the apply context, but
still perform a sanity check to ensure that the state be used is
equivalent.
@jbardin jbardin closed this Jul 17, 2017
@jbardin jbardin deleted the jbardin/apply-plan-state branch July 17, 2017 14:55
@ghost
Copy link

ghost commented Apr 8, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant