Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/17742
I have submitted PR for ALS optimization with GEMM. and it is ready for
review.
The performance is about 50% improvement comparing with the master method.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18624
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/18624
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79597/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18624
**[Test build #79597 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79597/testReport)**
for PR 18624 at commit
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/18620
Hi @srowen , I have added Test Suite for BoundedPriorityQueue. 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18620
**[Test build #79604 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79604/testReport)**
for PR 18620 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18620
**[Test build #79603 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79603/testReport)**
for PR 18620 at commit
Github user heary-cao commented on the issue:
https://github.com/apache/spark/pull/18555
@gatorsmile
supplementary test case to (v => v == 0 || (1024 <= v && v < 65536).
please review it again.
thank you.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18555
**[Test build #79602 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79602/testReport)**
for PR 18555 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18633
**[Test build #79601 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79601/testReport)**
for PR 18633 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/18633
[SPARK-21411][YARN] Lazily create FS within kerberized UGI to avoid token
acquiring failure
## What changes were proposed in this pull request?
In the current
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18629
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79595/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18629
Merged build finished. Test FAILed.
---
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/18629
**[Test build #79595 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79595/testReport)**
for PR 18629 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/18613
@felixcheung We don't silently drop features, we use ```handleInvalid``` to
let users decide how to handle invalid features or label. The behavior is
consistent with Scala which supports to
Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/18388
@tgravescs
Thanks a lot for advice.
> the flow control part should allow everyone to start fetching without
rejecting a bunch, especially if the network can't push it out that fast
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18503
@tdas @marmbrus @zsxwing could you please let us know any impacts by change
of `FixedLengthRowBasedKeyValueBatch`? Can we change this structure?
---
If your project is set up for it, you can reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18571
**[Test build #79600 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79600/testReport)**
for PR 18571 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18632
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
GitHub user gczsjdy opened a pull request:
https://github.com/apache/spark/pull/18632
Reset BufferHolder while initialize an UnsafeRowWriter
## What changes were proposed in this pull request?
`UnsafeRowWriter`'s construtor should contain `BufferHolder.reset` to make
the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18428
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/18428
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79596/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18428
**[Test build #79596 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79596/testReport)**
for PR 18428 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18631
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
GitHub user apapi opened a pull request:
https://github.com/apache/spark/pull/18631
[SPARK-SPARK-21410][CORE] RangePartitioner.numPartitions is wrong if â¦
â¦the number of elements in RDD is less than number of partitions
## What changes were proposed in this pull
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18630
**[Test build #79599 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79599/testReport)**
for PR 18630 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18630
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79599/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18630
Merged build finished. Test FAILed.
---
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/18630
**[Test build #79599 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79599/testReport)**
for PR 18630 at commit
Github user heary-cao commented on the issue:
https://github.com/apache/spark/pull/18555
@gatorsmile
sorry, Do you means ` > 0 or >= 0` also needs to be added?
I just added a test case to `(v => v == 0 || (1024 <= v && v < 65536)`
test case: `test("blockManager port
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18630
Merged build finished. Test FAILed.
---
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/18630
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79598/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18630
**[Test build #79598 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79598/testReport)**
for PR 18630 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18468
ping @cloud-fan
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18630
**[Test build #79598 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79598/testReport)**
for PR 18630 at commit
Github user skonto commented on the issue:
https://github.com/apache/spark/pull/18630
@vanzin pls review.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18503
This PR we changed `FixedLengthRowBasedKeyValueBatch`, I want to know if it
has some external impacts, like checkpoint data, or it's just used internally?
---
If your project is set up for it,
GitHub user skonto opened a pull request:
https://github.com/apache/spark/pull/18630
[SPARK-12559][SPARK SUBMIT] fix --packages for standalone
## What changes were proposed in this pull request?
Fixes --packages flag for the standalone mode.
## How was this patch
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18624
**[Test build #79597 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79597/testReport)**
for PR 18624 at commit
Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/18619
Yes this PR is a trivial Improvement for me. i will closed it if this has
side-effects exactly. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18428
**[Test build #79596 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79596/testReport)**
for PR 18428 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18444
BTW, I guess it'd be nicer if we get a sign-off from @davies if you have
some bandwidth to deal with this meanwhile.
---
If your project is set up for it, you can reply to this email and have
Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/18619
I just use `mvn checkstyle:check` ,which contains output files with
`basedir`, to check whether the `basedir` is correct with this PR.
Could you please specify the affect exactly as you
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18629
**[Test build #79595 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79595/testReport)**
for PR 18629 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17150
@srowen @JoshRosen After thinking more about it, will this PR make it
harder to backport bug fixes PRs to the previous branch? I did a little search
and seems we broke scala 2.10 a little
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/18629#discussion_r127367136
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamingQueryStatusAndProgressSuite.scala
---
@@ -33,16 +33,10 @@ import
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17848
cc @cloud-fan @sameeragarwal
---
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 tdas opened a pull request:
https://github.com/apache/spark/pull/18629
[SPARK-21409][SS] Expose state store memory usage in SQL metrics and
progress updates
## What changes were proposed in this pull request?
Currently, there is no tracking of memory usage of
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18444
BTW, I wouldn't mind if we go merge this meanwhile. I trust @ueshin's
judgement.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18444
I will help double check within coming three or four days (for me it takes
a quite while to debug and double check this case ...)
---
If your project is set up for it, you can reply to this
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18444
@HyukjinKwon, @holdenk, Could you double-check the way to handle an array
of typecode `'c'` please?
I'm not exactly sure this can cover all cases.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17848
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/17848
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79594/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17848
**[Test build #79594 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79594/testReport)**
for PR 17848 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18617
Hi, All.
Can we have this on `branch-2.2`, too?
---
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18571
```SQL
SELECT x'00' < x'0f'
SELECT x'00' < x'ff'
```
Could you add the above queries to a new `comparator.sql` file?
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18547
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/18547
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79591/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18547
**[Test build #79591 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79591/testReport)**
for PR 18547 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18617
---
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 the feature is
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18617
Merging 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,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17848
**[Test build #79594 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79594/testReport)**
for PR 17848 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18617
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79593/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18617
**[Test build #79593 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79593/testReport)**
for PR 18617 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18617
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/18617
**[Test build #79593 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79593/testReport)**
for PR 18617 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18628
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79592/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18628
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/18628
**[Test build #79592 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79592/testReport)**
for PR 18628 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18628
**[Test build #79592 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79592/testReport)**
for PR 18628 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/18628
[SPARK-21407][ThriftServer] Add spnego auth support for ThriftServer
thrift/http protocol
## What changes were proposed in this pull request?
Spark ThriftServer doesn't support spnego
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18555
@heary-cao Sorry, I did not find the test cases. Not comfortable to merge
the PR without the test cases.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user skonto commented on the issue:
https://github.com/apache/spark/pull/18587
thnx @vanzin I am working on some code for the standalone 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18515
@maver1ck Any update?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18627
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79590/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18627
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/18627
**[Test build #79590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79590/testReport)**
for PR 18627 at commit
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127321876
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127321136
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127319048
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127317541
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18547
**[Test build #79591 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79591/testReport)**
for PR 18547 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18547
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 if the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127314530
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18617#discussion_r127309324
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala
---
@@ -192,16 +193,29 @@ private[spark] class Client(
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18547
Jenkins, test 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
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18617#discussion_r127299428
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala
---
@@ -192,16 +193,29 @@ private[spark] class Client(
*
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18626
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/18626
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79589/
Test PASSed.
---
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127298989
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18626
**[Test build #79589 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79589/testReport)**
for PR 18626 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18621
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79588/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18621
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/18621
**[Test build #79588 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79588/testReport)**
for PR 18621 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127293947
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -674,6 +671,43 @@ private[spark] class
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127293531
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -90,6 +90,18 @@ private[spark] class
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127294479
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala
---
@@ -674,6 +671,43 @@ private[spark] class
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18616#discussion_r127295807
--- Diff:
core/src/main/scala/org/apache/spark/deploy/security/HadoopDelegationTokenManager.scala
---
@@ -42,7 +42,7 @@ import
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18627
**[Test build #79590 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79590/testReport)**
for PR 18627 at commit
GitHub user kiszk opened a pull request:
https://github.com/apache/spark/pull/18627
[BACKPORT-2.1][SPARK-19104][SQL] Lambda variables in ExternalMapToCatalyst
should be global
## What changes were proposed in this pull request?
This PR is backport of #18418 to Spark 2.1.
1 - 100 of 220 matches
Mail list logo
