refactor(meta): simplify InflightActorInfo and extract InflightGraphInfo #17956
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Previously, we include many inflight status of the running streaming graph in
InflightActorInfo
. In #17735 where we may have multiple partial graphs, we will assign a such struct to each partial graph to track their inflight statuses. Therefore, theInflightActorInfo
will rename toInflightGraphInfo
, and two global info fields,node_map
andmv_depended_subscriptions
, will be removed from the struct. Thenode_map
will be discarded, and we will change to use thenode_map
stored inActiveStreamingWorker
. Themv_depended_subscriptions
will be maintained separately in a newly introduced structInflightSubscriptionInfo
.In
CommandContext
, we won't hold theInflightActorInfo
any more. We will instead just hold its fields that we will previously access fromCommandContext
.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.