Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14072
Merging in master. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14072
**[Test build #3167 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3167/consoleFull)**
for PR 14072 at commit
Github user MasterDDT commented on the issue:
https://github.com/apache/spark/pull/14072
Yeah its in `StageInfo.stageId` from the `SparkListener` events. Our use
case is that we use FIFO scheduling (jobs fully utilize the cluster so parallel
doesnt help), but I want to listen for the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14072
**[Test build #3167 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3167/consoleFull)**
for PR 14072 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14072
Looks fine to me. Do we expose stage ID anywhere else?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user MasterDDT commented on the issue:
https://github.com/apache/spark/pull/14072
cc @srowen @rxin
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14072
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
