Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
merged to master and 2.4
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail:
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
If no other comments, I'll commit this? I'll leave it open for a bit longer
---
-
To unsubscribe, e-mail:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98269/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98269 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98269/testReport)**
for PR 22852 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
added sections to the resource manager sections.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98269 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98269/testReport)**
for PR 22852 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
I can add a note here for deployments here and then we can do version
specific ones after
---
-
To unsubscribe, e-mail:
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22852
I think these are good changes. In a separate PR for the versions-specific
docs, we could add a similar note to
https://spark.apache.org/docs/latest/spark-standalone.html as much of the
security
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98267 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98267/testReport)**
for PR 22852 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98267/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
Updated to have a section on security in the quickstart and overview, let
me know what you think and if wording needs updated. If this ok I can followup
with something on the website
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98267 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98267/testReport)**
for PR 22852 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22852
A quick pointer to security issues in other key places sounds good. As long
as it is increasing the chance users understand the specific issue and isn't
more general text to skip past, it is helping
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
I would be fine with adding it more places, including perhaps the overview
page: http://spark.apache.org/docs/latest/ and quick start pages.
Perhaps we should agree upon the wording here
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
I would rather see someone more familiar with K8s that uses it document it.
---
-
To unsubscribe, e-mail:
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22852
I don't feel strongly about it; go ahead.
If someone lands on this page, do they pretty easily come away with the
impression they need to set spark.authenticate and network security if they
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
so I had filed a jira to update mesos docs more detail about security
things (https://issues.apache.org/jira/browse/SPARK-25024) which I need to
follow up on, but I didn't file one for k8s. It
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/22852
I looked at the existing docs after I wrote my comment and saw that
paragraph. I think it's fine, maybe just in need of some update now that we
have k8s, although I'm not sure yet how
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
we can add stronger wording for standalone if you want, I know the text
was recently updated (I believe by you) to have the below:
> For other resource managers,
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/22852
I'm fine with this, although I wonder if having a stronger wording about
Spark standalone just not being secure would be better. Even if you enable
auth, everybody needs to know the same auth
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
the intention is not a we told you so, its meant to grab their attention
and to get people to think about it because in the end it is their
responsibility in my opinion.
I'm fine if you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98091/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98091 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98091/testReport)**
for PR 22852 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22852
I get it, the "it's your responsibility" stance, and it is. For any risk
there's a sentence in this doc we could point to and say, "see, told you". If
we're going to make a change here, adding
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98091 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98091/testReport)**
for PR 22852 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98090/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98090 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98090/testReport)**
for PR 22852 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22852
**[Test build #98090 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/98090/testReport)**
for PR 22852 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22852
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/22852
@vanzin @srowen
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail:
41 matches
Mail list logo
