Skip to content

Conversation

@mgaido91
Copy link
Contributor

What changes were proposed in this pull request?

SPARK-20648 introduced the status SKIPPED for the stages. On the UI, previously, skipped stages were shown as PENDING; after this change, they are not shown on the UI.

The PR introduce a new section in order to show also SKIPPED stages in a proper table.

How was this patch tested?

manual tests

@mgaido91
Copy link
Contributor Author

cc @vanzin @zsxwing

@SparkQA
Copy link

SparkQA commented Feb 21, 2018

Test build #87587 has finished for PR 20651 at commit 5f5d0da.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

Copy link
Contributor

@vanzin vanzin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be nice to update UISeleniumSuite to add a unit test. I checked an it only tests skipped stages on the jobs page, but not on the stages list.

}
if (shouldShowSkippedStages) {
content ++=
<span id="skipped" class="collapse-aggregated-allSkippedStages collapse-table"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see things like collapse-aggregated-allCompletedStages are mentioned in webui.js, so probably this one should be added there.

This is kinda past the point where this block should be refactored (it's repeated 5 times now), but probably ok for a 2.3 change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, I added the UT. I think we can create a new JIRA/followup PR to resolve the code redundancy issue you rightly pointed out, what do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good to clean things up in a follow-up.

@zsxwing
Copy link
Member

zsxwing commented Feb 21, 2018

@mgaido91 Spark 2.2 doesn't show skipped stages either. I think this is fine since most of people don't care about them. I posted the root cause and fixed in #20656

@mgaido91
Copy link
Contributor Author

@zsxwing SKIPPED stages were previously shown as PENDING. Despite I agree that your fix is needed, I think this is needed too. Do you agree @vanzin?

@SparkQA
Copy link

SparkQA commented Feb 22, 2018

Test build #87615 has finished for PR 20651 at commit e04bf24.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@mgaido91
Copy link
Contributor Author

Jenkins, retest this please

@SparkQA
Copy link

SparkQA commented Feb 22, 2018

Test build #87617 has finished for PR 20651 at commit e04bf24.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@vanzin
Copy link
Contributor

vanzin commented Feb 22, 2018

LGTM, merging to master / 2.3.

@vanzin
Copy link
Contributor

vanzin commented Feb 22, 2018

Merged to master, but there were conflicts in 2.3; please open a separate PR for the backport.

@asfgit asfgit closed this in 87293c7 Feb 22, 2018
@mgaido91
Copy link
Contributor Author

thanks @vanzin I created the PR for the backport. Thanks.

mgaido91 added a commit to mgaido91/spark that referenced this pull request Feb 23, 2018
SPARK-20648 introduced the status `SKIPPED` for the stages. On the UI, previously, skipped stages were shown as `PENDING`; after this change, they are not shown on the UI.

The PR introduce a new section in order to show also `SKIPPED` stages in a proper table.

manual tests

Author: Marco Gaido <[email protected]>

Closes apache#20651 from mgaido91/SPARK-23475.
asfgit pushed a commit that referenced this pull request Feb 27, 2018
…code

As suggested in #20651, the code is very redundant in `AllStagesPage` and modifying it is a copy-and-paste work. We should avoid such a pattern, which is error prone, and have a cleaner solution which avoids code redundancy.

existing UTs

Author: Marco Gaido <[email protected]>

Closes #20663 from mgaido91/SPARK-23475_followup.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants