Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15505
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73520/
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17083
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73498/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17083
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/15505
**[Test build #73520 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73520/testReport)**
for PR 15505 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/73501/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17083
**[Test build #73498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73498/testReport)**
for PR 17083 at commit
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 skonto commented on the issue:
https://github.com/apache/spark/pull/17031
Ok like the Cassandra case you mean right?
---
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/17086
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/16478
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73519/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17086
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73529/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16478
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/17086
**[Test build #73529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73529/testReport)**
for PR 17086 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16478
**[Test build #73519 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73519/testReport)**
for PR 16478 at commit
Github user skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/17031#discussion_r103287098
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosFineGrainedSchedulerBackend.scala
---
@@ -24,6 +24,7 @@
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16990
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73511/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16990
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/16990
**[Test build #73511 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73511/testReport)**
for PR 16990 at commit
Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/17031
Given the concerns about the dispatcher being stuck in a suppressed state,
I'm going to solve this a different way. I'm going to increase the default
offer decline timeout to 120s and make it
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14299
You also should file a bug and reference it from the PR title.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17084
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73526/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17084
**[Test build #73526 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73526/testReport)**
for PR 17084 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17084
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/17039
How about the more pragmatic approach. I think relation algebra only
guarantees ordering when an order by is the top level operation. Why not just
check that, and if we find one, add all output
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17001
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73510/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17001
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/17001
**[Test build #73510 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73510/testReport)**
for PR 17001 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17071
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73506/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17071
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 skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/17031#discussion_r103281854
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -582,141 +688,33 @@
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17071
**[Test build #73506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73506/testReport)**
for PR 17071 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73516/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16809
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/16809
**[Test build #73516 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73516/testReport)**
for PR 16809 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17039
The major issue is we do not know the original intention of users' query.
The query might purposely check whether the result set is sorted or not. Thus,
the existing test suite design is
Github user skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/17031#discussion_r103281366
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -737,13 +735,75 @@
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13326
@mgummelt /@tnachen, can you have a look into this?
---
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 devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/13143
@mgummelt /@tnachen, can you have a look into this?
---
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 skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/17031#discussion_r103280797
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -737,13 +735,75 @@
Github user skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/17031#discussion_r103280133
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/deploy/mesos/ui/MesosClusterPage.scala
---
@@ -32,7 +32,7 @@ private[mesos] class
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/16782
also, using the `inspection` module it would be possible to check if the
wrapped function is a method. Then we wouldn't need to just make that
assumption.
---
If your project is set up for
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17039
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/17039
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73508/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17079
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73502/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17079
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/17039
**[Test build #73508 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73508/testReport)**
for PR 17039 at commit
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/16782
Thanks @jkbradley and @davies for reviewing. This fix still seems a little
hacky to me and you could still possibly run into trouble if you call a nested
wrapped function and don't consume the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17079
**[Test build #73502 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73502/testReport)**
for PR 17079 at commit
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/16476
@gczsjdy : I had one comment in past about `genIfElseStructure` but after
giving more thought, I was not able to think about a better way to do that. I
am fine withthe current version of code
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/17083#discussion_r103278713
--- Diff: core/src/main/scala/org/apache/spark/ui/JettyUtils.scala ---
@@ -378,7 +378,8 @@ private[spark] object JettyUtils extends Logging {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17082
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/17083#discussion_r103279006
--- Diff: core/src/test/scala/org/apache/spark/ui/UISuite.scala ---
@@ -267,8 +267,11 @@ class UISuite extends SparkFunSuite {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17082
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73499/
Test PASSed.
---
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/16784#discussion_r103278706
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LinearSVCSuite.scala ---
@@ -220,12 +246,13 @@ object LinearSVCSuite {
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/16784#discussion_r103278715
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LinearSVCSuite.scala ---
@@ -234,7 +261,12 @@ object LinearSVCSuite {
val yD
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17082
**[Test build #73499 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73499/testReport)**
for PR 17082 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/16784#discussion_r103278729
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LinearSVCSuite.scala ---
@@ -203,6 +227,8 @@ class LinearSVCSuite extends SparkFunSuite
Github user BryanCutler commented on a diff in the pull request:
https://github.com/apache/spark/pull/16782#discussion_r103277884
--- Diff: python/pyspark/__init__.py ---
@@ -96,9 +96,11 @@ def keyword_only(func):
"""
@wraps(func)
def wrapper(*args,
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/16782#discussion_r103276349
--- Diff: python/pyspark/__init__.py ---
@@ -96,9 +96,11 @@ def keyword_only(func):
"""
@wraps(func)
def wrapper(*args, **kwargs):
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17064#discussion_r103277557
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/CacheManager.scala ---
@@ -168,15 +168,16 @@ class CacheManager extends Logging {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17077
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/17077
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73527/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17077
**[Test build #73527 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73527/testReport)**
for PR 17077 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17086
**[Test build #73529 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73529/testReport)**
for PR 17086 at commit
Github user imatiach-msft commented on the issue:
https://github.com/apache/spark/pull/16557
I've created 3 PRs, located here:
https://github.com/apache/spark/pull/17084
https://github.com/apache/spark/pull/17085
https://github.com/apache/spark/pull/17086
---
If your
GitHub user imatiach-msft opened a pull request:
https://github.com/apache/spark/pull/17086
[SPARK-18693][ML][MLLIB] ML Evaluators should use weight column - added
weight column for multiclass classification evaluator
## What changes were proposed in this pull request?
The
GitHub user imatiach-msft opened a pull request:
https://github.com/apache/spark/pull/17085
[SPARK-18693][ML][MLLIB] ML Evaluators should use weight column - added
weight column for regression evaluator
## What changes were proposed in this pull request?
The evaluators
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/17076#discussion_r103276904
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LinearSVC.scala ---
@@ -440,19 +440,9 @@ private class LinearSVCAggregator(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17085
**[Test build #73528 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73528/testReport)**
for PR 17085 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17075
I think we should fix `changePrecison` to return a new instance instead of
updating itself.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/16290#discussion_r103276097
--- Diff: R/pkg/R/sparkR.R ---
@@ -376,6 +377,12 @@ sparkR.session <- function(
overrideEnvs(sparkConfigMap, paramMap)
}
+ #
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16330
Its a bit tricky to ask users permission during installation (actually I'm
not sure how we can create such an option ?) -- I think a viable option could
be to do add `logWarning` that shows where
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17077
**[Test build #73527 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73527/testReport)**
for PR 17077 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17084
**[Test build #73526 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73526/testReport)**
for PR 17084 at commit
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16842#discussion_r103274162
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/KinesisBackedBlockRDD.scala
---
@@ -212,7 +214,7 @@ class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16910
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/16910
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73513/
Test PASSed.
---
GitHub user imatiach-msft opened a pull request:
https://github.com/apache/spark/pull/17084
[SPARK-18693][ML][MLLIB] ML Evaluators should use weight column - added
weight column for binary classification evaluator
## What changes were proposed in this pull request?
The
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16910
**[Test build #73513 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73513/testReport)**
for PR 16910 at commit
Github user imatiach-msft closed the pull request at:
https://github.com/apache/spark/pull/16557
---
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 imatiach-msft commented on the issue:
https://github.com/apache/spark/pull/16557
ok, I will close this and create three new PRs, one for each of the
evaluators
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17052
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/17052
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73507/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17052
**[Test build #73507 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73507/testReport)**
for PR 17052 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16557
**[Test build #73525 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73525/testReport)**
for PR 16557 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16971#discussion_r103270963
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/stat/StatFunctions.scala
---
@@ -91,7 +100,13 @@ object StatFunctions extends Logging
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16793
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73524/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16793
**[Test build #73524 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73524/testReport)**
for PR 16793 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16793
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 brkyvz commented on the issue:
https://github.com/apache/spark/pull/16929
Thanks @HyukjinKwon took a pass. My comments are mainly:
1. We don't need to support APIs for both `StructType` and `ArrayType`. I
would rather just add an API for `DataType` and `require`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17077
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73523/
Test FAILed.
---
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16842
@Gauravshah Can you please comment on how much faster this PR improved your
recovery time?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17077
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/17077
**[Test build #73523 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73523/testReport)**
for PR 17077 at commit
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16929#discussion_r103268734
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/json/JacksonParser.scala
---
@@ -39,7 +39,12 @@ private[sql] class
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16929#discussion_r103268655
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/jsonExpressions.scala
---
@@ -480,36 +480,79 @@ case class
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/16929#discussion_r103268156
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/jsonExpressions.scala
---
@@ -480,36 +480,79 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17076
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/17076
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73505/
Test PASSed.
---
401 - 500 of 613 matches
Mail list logo
