Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14148
**[Test build #62144 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62144/consoleFull)**
for PR 14148 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62141/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14148
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/14148
**[Test build #62141 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62141/consoleFull)**
for PR 14148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14148
**[Test build #62143 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62143/consoleFull)**
for PR 14148 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r70380596
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/OptimizeMetadataOnlyQuerySuite.scala
---
@@ -0,0 +1,122 @@
+/*
+ * Licensed to
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r70380410
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/OptimizeMetadataOnlyQuery.scala
---
@@ -0,0 +1,162 @@
+/*
+ * Licensed to the
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14148
Did a quick check. My understanding is wrong. We did the schema inference
when creating the table. Let me fix it. Thanks!
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14146
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 sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/14146
LGTM
---
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/14146
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62139/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14146
**[Test build #62139 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62139/consoleFull)**
for PR 14146 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14148
@rxin The created table could be empty. Thus, we are unable to cover all
the cases even if we try schema inference when creating tables. You know, this
is just my understanding. No clue about
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14116
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62140/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14116
**[Test build #62140 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62140/consoleFull)**
for PR 14116 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14116
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14120
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14080
**[Test build #3185 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3185/consoleFull)**
for PR 14080 at commit
Github user rxin closed the pull request at:
https://github.com/apache/spark/pull/13901
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/14120
Merging in 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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/14143
LGTM!
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/14148
Shouldn't schema inference run as soon as the table is created?
---
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/13494
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62137/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13494
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/13494
**[Test build #62137 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62137/consoleFull)**
for PR 13494 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14139
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/14139
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62142/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14139
**[Test build #62142 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62142/consoleFull)**
for PR 14139 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11317
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14028
@yhuai Could you take another 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 project does not have this feature
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/11317
lgtm. 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14139
**[Test build #62142 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62142/consoleFull)**
for PR 14139 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14144
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/14144
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62135/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14144
**[Test build #62135 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62135/consoleFull)**
for PR 14144 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14139
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/14139
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62136/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14139
**[Test build #62136 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62136/consoleFull)**
for PR 14139 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
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/14079
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62134/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14079
**[Test build #62134 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62134/consoleFull)**
for PR 14079 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14148
**[Test build #62141 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62141/consoleFull)**
for PR 14148 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/14148
[SPARK-16482] [SQL] Describe Table Command for Tables Requiring Runtime
Inferred Schema
What changes were proposed in this pull request?
If we create a table pointing to a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14138
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/14138
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62133/
Test PASSed.
---
Github user yanboliang closed the pull request at:
https://github.com/apache/spark/pull/14052
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14138
**[Test build #62133 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62133/consoleFull)**
for PR 14138 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14116
**[Test build #62140 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62140/consoleFull)**
for PR 14116 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14146
**[Test build #62139 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62139/consoleFull)**
for PR 14146 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14146
cc @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 and wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14116
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62138/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14116
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14144
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/14144
Merging in master/2.0.
---
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 lovexi commented on the issue:
https://github.com/apache/spark/pull/14080
Thank you for reminding me this. Already updated PR description and add
more details.
cc @rxin
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14080
**[Test build #3185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3185/consoleFull)**
for PR 14080 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14144
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62129/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14144
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 rxin commented on the issue:
https://github.com/apache/spark/pull/14080
Can you update the pull request description? It is now outdated.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14144
**[Test build #62129 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62129/consoleFull)**
for PR 14144 at commit
Github user lovexi commented on the issue:
https://github.com/apache/spark/pull/14080
Restart test, 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 so,
Github user lovexi commented on the issue:
https://github.com/apache/spark/pull/14080
@rxin Thank you for letting me know this. That saves me a lot of time on
testing..
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14146
**[Test build #3184 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3184/consoleFull)**
for PR 14146 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14045
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62130/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14045
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/14045
**[Test build #62130 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62130/consoleFull)**
for PR 14045 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14146
**[Test build #3183 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3183/consoleFull)**
for PR 14146 at commit
Github user lianhuiwang commented on the issue:
https://github.com/apache/spark/pull/13494
@cloud-fan @hvanhovell about getPartitionAttrs() It has a improve place
that we can define it in relation node. but now relation node has not this
function. how about added in follow-up PRs?
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13494
**[Test build #62137 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62137/consoleFull)**
for PR 13494 at commit
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r70370384
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/OptimizeMetadataOnlyQuery.scala
---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the
Github user jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/14012#discussion_r70370161
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -1086,6 +1086,28 @@ object PruneFilters extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14141
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62127/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14141
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/14141
**[Test build #62127 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62127/consoleFull)**
for PR 14141 at commit
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r70369134
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/OptimizeMetadataOnlyQuery.scala
---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r70368905
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/OptimizeMetadataOnlyQuery.scala
---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13494#discussion_r70368861
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/OptimizeMetadataOnlyQuery.scala
---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14139
**[Test build #62136 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62136/consoleFull)**
for PR 14139 at commit
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13704#discussion_r70368410
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/SimplifyCastsSuite.scala
---
@@ -0,0 +1,78 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14144
**[Test build #62135 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62135/consoleFull)**
for PR 14144 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14144
LGTM pending Jenkins.
---
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 kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13704#discussion_r70367470
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/benchmark/PrimitiveArrayBenchmark.scala
---
@@ -0,0 +1,84 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14079
**[Test build #62134 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62134/consoleFull)**
for PR 14079 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/14079
discussed this offline with @vanzin, realized that actually with the latest
design, it doesn't make sense to have so many maps inside one
`BlacklistTracker` -- a lot of info is now intended to only
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/13894#discussion_r70367155
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/CrossValidator.scala ---
@@ -56,7 +56,10 @@ private[ml] trait CrossValidatorParams extends
Github user petermaxlee commented on a diff in the pull request:
https://github.com/apache/spark/pull/14138#discussion_r70366868
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/CallMethodViaReflection.scala
---
@@ -0,0 +1,166 @@
+/*
+ *
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14147
**[Test build #62132 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62132/consoleFull)**
for PR 14147 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14147
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62132/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14147
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14143
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14138
**[Test build #62133 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62133/consoleFull)**
for PR 14138 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14147
**[Test build #62132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62132/consoleFull)**
for PR 14147 at commit
GitHub user jkbradley opened a pull request:
https://github.com/apache/spark/pull/14147
[SPARK-14812][ML][MLLIB][PYTHON] Experimental, DeveloperApi annotation
audit for ML
## What changes were proposed in this pull request?
General decisions to follow, except where noted:
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14138#discussion_r70366108
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/CallMethodViaReflection.scala
---
@@ -0,0 +1,166 @@
+/*
+ *
Github user petermaxlee commented on a diff in the pull request:
https://github.com/apache/spark/pull/14138#discussion_r70366065
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/CallMethodViaReflectionSuite.scala
---
@@ -0,0 +1,102 @@
+/*
+
Github user petermaxlee commented on a diff in the pull request:
https://github.com/apache/spark/pull/14138#discussion_r70366073
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/CallMethodViaReflection.scala
---
@@ -0,0 +1,166 @@
+/*
+ *
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/14143
@zsxwing
I am merging this critical bug fix to master and 2.0. Feel free to leave
reviews and I will address them in follow up PRs.
---
If your project is set up for it, you can reply to
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14138#discussion_r70365738
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/CallMethodViaReflectionSuite.scala
---
@@ -0,0 +1,102 @@
+/*
+ *
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14138#discussion_r70365507
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/CallMethodViaReflection.scala
---
@@ -0,0 +1,166 @@
+/*
+ *
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14088
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62128/
Test PASSed.
---
1 - 100 of 642 matches
Mail list logo
