yliou
yliou
cc @gengliangwang
cc @gengliangwang would this feature be of interest?
cc @tgravescs would this feature be of interest?
@tgravescs do you have time to take a quick look?
Thanks for the feedback comments so far. 1. I originally added the list of completed stages for convenience on the SQL UI. Do you think it's worth removing the list...
> sorry, I missed your response. > > After looking some more the list of jobs can get very long as well. I'm fine with leaving the list of stages...
> [SPARK38617.txt](https://github.com/apache/spark/files/8326833/SPARK38617.txt) is in rich text format. It would be easier to review if it was plain text. Attached new file with plain text format.
> #35856 has tried the similar things although at present it miss the details of the compile time for each phase. And its scope also includes the AQE, I think...
@ulysses-you got it. I think it is possible to re-use the same code path but not sure how that'd work with ExecutionPage.scala to get the info on the UI.
> Can we use a more meaningful JSON field names? E.g., `value` -> `timeMs` `name` -> `phase` > > ``` > { > “phase” : “optimization”, > “timeMs” : “373"...