Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
@elgalu feel free to try picking it back up, I was a fan of it when
reviewing it "back in the day"
---
-
To unsubscribe,
Github user elgalu commented on the issue:
https://github.com/apache/spark/pull/17455
Such a pity this was PR was abandoned, I've just spend like 2 hours hacking
nginx to get over this problem...
---
-
To
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17455
I'm going to close this PR because it goes stale, please feel free to
reopen it or open another PR if anyone have more thoughts on this issue.
---
Github user okoethibm commented on the issue:
https://github.com/apache/spark/pull/17455
@jiangxb1987 I've stopped working on Spark related efforts a while ago and
will not be following up on this PR any more. Anyone interested is free to take
over.
---
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17455
@okoethibm Have you got any time to rebase this PR to the latest master?
---
-
To unsubscribe, e-mail:
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
Before this can move forward it needs to be updated, but I can tell you now
that since this is a new feature and not a bug fix this will never make it into
2.1.x or 2.2.x, the earliest you'll see
Github user andrelu commented on the issue:
https://github.com/apache/spark/pull/17455
Hello, any update on this issue? is it going to be available on versions
2.1.x?
Tks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
#18499 was just merged, you'll need to update this to match the new code if
you hope to get reinvigorate interest
---
If your project is set up for it, you can reply to this email and have your
Github user sayeaud commented on the issue:
https://github.com/apache/spark/pull/17455
Would love to get this in for the next release, currently I'm using a
variant of https://github.com/aseigneurin/spark-ui-proxy to work around this
issue...
---
If your project is set up for it,
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
@vanzin I noticed this stalled after I reviewed it, mind taking a look?
---
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
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17455
ok to test
---
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
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17455
retest this please
---
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
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
Usually new features aren't added to branches after they've been cut, and
almost never after an rc has been cut. So given branch-2.2 was cut over a month
ago and we're about to cut rc3, I'm
Github user agsimeonov commented on the issue:
https://github.com/apache/spark/pull/17455
Any chance this can get into v2.2.0? I am using Spark in Docker with nginx
reverse proxy and this would help immensely.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17455
**[Test build #3730 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3730/testReport)**
for PR 17455 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17455
**[Test build #3730 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3730/testReport)**
for PR 17455 at commit
Github user BartekH commented on the issue:
https://github.com/apache/spark/pull/17455
Any update? It's very urgent case.
---
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
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
It seems it didn't take @holdenk ok, @vanzin mind okaying this to test?
---
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
Github user okoethibm commented on the issue:
https://github.com/apache/spark/pull/17455
@ajbozarth Any other comments on this PR? Why is it not testing even though
it has an "ok to test"?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17455
Jenkins OK to test.
---
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 ajbozarth commented on the issue:
https://github.com/apache/spark/pull/17455
I'm still taking some time looking at this, but while I do, @vanzin and
@tgravescs you two reviewed the original reverse proxy pr, could you take a
look? Also @gurvindersingh want to take a look?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17455
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
22 matches
Mail list logo
