Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/17790
cc @yhuai
---
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, or if
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17790
> it will impact the classpath for user apps
Jetty is shaded in Spark.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17790
CC @zsxwing as it touches Jetty.
This is probably OK, even though it will impact the classpath for user apps
and Jetty could have some non-trivial changes. I agree there's good reason to
do this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17790
**[Test build #76244 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76244/testReport)**
for PR 17790 at commit
Github user markgrover commented on the issue:
https://github.com/apache/spark/pull/17790
I am running unit tests locally and while the run hasn't finished, it's
looking pretty good so far. I think it'd be good to get Jenkins to run the
tests here anyways so putting a PR sooner than
