Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17080
thanks. One thing I realised last night is that logging the session token,
even at debug level, would have been a security risk. So it's very good that
the log statement got cut, even at the
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17080
Merged to master
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/17080
cc @vanzin
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17080
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73797/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17080
**[Test build #73797 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73797/testReport)**
for PR 17080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17080
**[Test build #73797 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73797/testReport)**
for PR 17080 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73765/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17080
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17080
**[Test build #73765 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73765/testReport)**
for PR 17080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17080
**[Test build #73765 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73765/testReport)**
for PR 17080 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17080
@srowen dont worry, been tracking this: I filed the JIRA. Core code is good
(i.e. property/env var names).
One thing to bear in mind, the existing code propagates the env vars even
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17080
\cc @srowen
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/17080
@steveloughran OK
---
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 steveloughran commented on the issue:
https://github.com/apache/spark/pull/17080
I agree. I was just checking the files to make sure the strings were
consistent/correct, rather than trusting the documentation
---
If your project is set up for it, you can reply to this
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17080
@steveloughran IMHO, there is no need to use
`org.apache.hadoop.fs.s3a.Constants` and
`com.amazonaws.SDKGlobalConfiguration`, otherwise we will import `hadoop-aws`
and `aws-java-sdk-core` into
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17080
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17080
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73501/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17080
**[Test build #73501 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73501/testReport)**
for PR 17080 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17080
**[Test build #73501 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73501/testReport)**
for PR 17080 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17080
LGTM. Verified option name in `org.apache.hadoop.fs.s3a.Constants` file;
env var name in `com.amazonaws.SDKGlobalConfiguration'
---
If your project is set up for it, you can reply to
21 matches
Mail list logo
