[SPARK-45204][CONNECT] Extend CommandPlugins to be trackable #42984
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.
What changes were proposed in this pull request?
Adding a
CommandPluginWithQueryPlanningTrackerinterface which extends the already existingCommandPlugininterface with aprocess()method that one can pass aQueryPlanningTrackerto.Why are the changes needed?
There is currently no way to track queries executed by a
CommandPlugin.Does this PR introduce any user-facing change?
Users now can also write trackable plugins by implementing the
CommandPluginWithQueryPlanningTracker. Since this extends theCommandPlugininterface such plugins are also backward-compatible to older versions of spark only knowing theCommandPlugininterface.How was this patch tested?
Test added.
Was this patch authored or co-authored using generative AI tooling?
No