Web console: show stages for MSQ compaction tasks#18545
Merged
cryptoe merged 2 commits intoapache:masterfrom Sep 23, 2025
Merged
Web console: show stages for MSQ compaction tasks#18545cryptoe merged 2 commits intoapache:masterfrom
cryptoe merged 2 commits intoapache:masterfrom
Conversation
cryptoe
approved these changes
Sep 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR makes it so that an MSQ based compaction task will use the stages pane to render the report rather than just showing the JSON.
New behaviour:
Old behaviour:
The way I achieve this is a little ugly but I could not think of a better way without a big refactor.
I made a
ShowJsonOrStagescomponent that is likeShowJsonbut will show the stages UI if the data loaded looks like an MSQ report. Since this is a one off I think it is ok. In the future if we are going to have a lot ofShowJsonOrXthen might make sense to generalize somehow rather than making a component for everyX