Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16212
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/16212
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69858/
Test FAILed.
---
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16148
Yeah, 2.1 RC2 has been cut, but I think we still need to merge it into
branch-2.1, since it's possible we have new RC. Even if RC2 passed voting, we
will have 2.1.1, 2.1.2, ... which need this
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/9352
Opened two new [WIP] PRs to fix this issue using different approaches.
https://github.com/apache/spark/pull/16208
https://github.com/apache/spark/pull/16209
Closing this PR.
Github user sureshthalamati closed the pull request at:
https://github.com/apache/spark/pull/9352
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16208
@rxin @joshrosen @srowen Which options are preferred for supporting
customized column types? Table-level JDBC option or column-level metadata
property? Thanks!
---
If your project is set up
GitHub user maropu opened a pull request:
https://github.com/apache/spark/pull/16213
[SPARK-18020][Streaming][Kinesis] Checkpoint SHARD_END to finish reading
closed shards
## What changes were proposed in this pull request?
This pr is to fix an issue occurred when resharding
Github user AnthonyTruchet commented on a diff in the pull request:
https://github.com/apache/spark/pull/16037#discussion_r91493798
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/optimization/LBFGS.scala ---
@@ -241,16 +241,24 @@ object LBFGS extends Logging {
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16017#discussion_r91495968
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/DecisionTreeClassifier.scala
---
@@ -52,33 +52,49 @@ class DecisionTreeClassifier
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16213
**[Test build #69860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69860/consoleFull)**
for PR 16213 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16212
Most fixes won't matter for Spark because Spark only uses some client-side
APIs. Is there a specific fix that's important?
It's generally OK to update through maintenance releases regularly,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16147
(note to myself) I tracked down where the paths are added. It seems mostly
they are added in
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16147
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16211
**[Test build #69857 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69857/consoleFull)**
for PR 16211 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16214
@felixcheung @shivaram
---
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/16214
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69861/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16214
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/16214
**[Test build #69861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69861/consoleFull)**
for PR 16214 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16148
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/16148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69862/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16148
**[Test build #69862 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69862/consoleFull)**
for PR 16148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16213
**[Test build #69863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69863/consoleFull)**
for PR 16213 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16161
> there is no type that is assignable to both mutable.Map and immutable.Map
Yea, and a general solution would be, remember the original type and create
that type when converting catalyst
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16213
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16068#discussion_r91526428
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveUDFSuite.scala
---
@@ -487,6 +489,26 @@ class HiveUDFSuite extends QueryTest
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16147
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16211
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/16211
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69857/
Test FAILed.
---
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16213
I'm looking into the failure.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16148
**[Test build #69862 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69862/consoleFull)**
for PR 16148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16214
**[Test build #69861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69861/consoleFull)**
for PR 16214 at commit
Github user Halawa13 commented on the issue:
https://github.com/apache/spark/pull/11871
Hello,
I'm new to programming pyspark, i have problem with this code
**from pyspark.ml.feature import StopWordsRemover
df = sc.createDataFrame([(0,["je", "suis", "malade",
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16148
---
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 a-roberts commented on the issue:
https://github.com/apache/spark/pull/16212
http://www.openwall.com/lists/oss-security/2016/11/29/1 mentions Hadoop
2.7.x users should upgrade to 2.7.3 and Hadoop 2.6.x users should upgrade to
2.6.5, so if our Hadoop users are moving up to
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16212
It sounds like that affects the HDFS NameNode, but Spark has nothing to do
with that.
It shouldn't be incompatible across maintenance releases in any event.
Hence occasionally bumping it is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16212
**[Test build #69858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69858/consoleFull)**
for PR 16212 at commit
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/16214
[[SPARK-18325]][SPARKR] Add example for using native R package.
## What changes were proposed in this pull request?
SparkR provides the ability to distribute the computations by
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16213
**[Test build #69860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69860/consoleFull)**
for PR 16213 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16213
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69860/
Test FAILed.
---
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14365
retest 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 and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #3478 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3478/consoleFull)**
for PR 16187 at commit
Github user yaooqinn commented on the issue:
https://github.com/apache/spark/pull/11045
Hi @winningsix, I am interesting in your idea, and i am confusing about
the field `userName` used in your code, 1)where is it be initialized? 2) is it
used for privilege checking?
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #3478 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3478/consoleFull)**
for PR 16187 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16212
**[Test build #69858 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69858/consoleFull)**
for PR 16212 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16209
@rxin @joshrosen @srowen Which options are preferred for supporting
customized column types? Table-level JDBC option or column-level metadata
property? Thanks!
---
If your project is set up
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16204
**[Test build #3477 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3477/consoleFull)**
for PR 16204 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16204
cc @ericl
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14365
**[Test build #69856 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69856/consoleFull)**
for PR 14365 at commit
GitHub user holdenk opened a pull request:
https://github.com/apache/spark/pull/16211
[SPARK-18576][PYTHON] Add basic TaskContext information to PySpark
## What changes were proposed in this pull request?
Adds basic TaskContext information to PySpark.
## How was
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16195
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69846/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16204
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69853/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16193
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69850/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16187
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69848/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16195
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/16207
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/16204
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/16208
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69849/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16193
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/14365
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/14365
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69852/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16208
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/16187
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/16207
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69847/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16204
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/16209
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69855/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16204
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69854/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16209
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 viirya commented on the issue:
https://github.com/apache/spark/pull/16115
ping @davies again
---
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 winningsix commented on the issue:
https://github.com/apache/spark/pull/11045
@yaooqinn thank you for your interest. It's required by Hive side at
SessionState. And it's not used for privilege check. Some companies have
already used this pull request in their product
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14365
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69856/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14365
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/16204
**[Test build #3477 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3477/consoleFull)**
for PR 16204 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14365
**[Test build #69856 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69856/consoleFull)**
for PR 14365 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/16017#discussion_r91484503
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/DecisionTreeClassifier.scala
---
@@ -52,33 +52,49 @@ class DecisionTreeClassifier
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16213
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/16213
**[Test build #69859 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69859/consoleFull)**
for PR 16213 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16213
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69859/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16213
**[Test build #69859 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69859/consoleFull)**
for PR 16213 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16211
**[Test build #69857 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69857/consoleFull)**
for PR 16211 at commit
GitHub user a-roberts opened a pull request:
https://github.com/apache/spark/pull/16212
[SPARK-18782] [BUILD] Bump Hadoop 2.6 version to use Hadoop 2.6.5
## What changes were proposed in this pull request?
Use Hadoop 2.6.5 for the Hadoop 2.6 profile, I see a bunch of fixes
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16193
As we can push down predicates through data source scan, those predicates
should be already pushed down if they are in the query plan above data source
scan node. This seems only work on ExistingRDD
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16193
If we really want to do this, I'd suggest to push down predicates to rdd
scan node during query planning stage. So we don't need to push down predicates
to SparkPlan like this.
---
If your project
Github user yaooqinn commented on the issue:
https://github.com/apache/spark/pull/11045
@winningsix Glad to hear from you. And we can only use this through Spark
ThriftServer, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91497545
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +435,57 @@ private[spark] class Executor(
}
/**
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16196
+1 on @srowen's suggestion. This change is not surgical at all. It is going
to be difficult to guarantee no behavior change. If anything I'd trade off
performance over correctness here.
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13944
**[Test build #3479 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3479/consoleFull)**
for PR 13944 at commit
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/13579#discussion_r91546575
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -349,6 +349,17 @@ class HistoryServerSuite extends
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/13579#discussion_r91546615
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -349,6 +349,17 @@ class HistoryServerSuite extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13579
**[Test build #69864 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69864/consoleFull)**
for PR 13579 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13579
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69864/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13579
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16187
> We currently rely on FileFormat implementations to override toString in
order to get a proper explain output. It'd be better to just depend on
shortName for those.
Looks the PR
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16115
good catch! Merging to master/2.1, 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 does not have this
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16214#discussion_r91561992
--- Diff: examples/src/main/r/native-r-package.R ---
@@ -0,0 +1,80 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16144
Ping @jaceklaskowski
---
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 daisukebe commented on the issue:
https://github.com/apache/spark/pull/16195
This doesn't look like correlating with my code change. Should I fix this,
@vanzin?
```
Traceback (most recent call last):
File "./dev/run-tests-jenkins.py", line 228, in
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16175#discussion_r91541946
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -115,7 +115,8 @@ abstract class SparkStrategies extends
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16214#discussion_r91561800
--- Diff: examples/src/main/r/native-r-package.R ---
@@ -0,0 +1,80 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16115
---
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
1 - 100 of 515 matches
Mail list logo
