Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114152745
Merged build started.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-114168411
@nemccarthy Yeah. This one should be in today. I am taking a final check
now.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-114173048
[Test build #35459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35459/consoleFull)
for PR 6039 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6864
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6857#issuecomment-114166208
@shivaram Yeah, ignore that error for now. I'll fix this soon with either a
Jenkins conf. change or by adding a dummy test file so that the check never
fails. In the
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/6857#issuecomment-114173331
@shivaram - I'll test it out now.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6932#issuecomment-114179767
LGTM. I am merging it to branch-1.4.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-114179593
LGTM. I am merging it 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
Github user nssalian commented on a diff in the pull request:
https://github.com/apache/spark/pull/6924#discussion_r32958837
--- Diff: docs/running-on-yarn.md ---
@@ -7,6 +7,53 @@ Support for running on [YARN (Hadoop
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-114186900
Merged build started.
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r32959777
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/api/r/SQLUtils.scala
---
@@ -43,24 +43,6 @@ private[r] object SQLUtils {
StructType(fields)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6894#issuecomment-114192264
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6894#issuecomment-114192311
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114161839
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-114172376
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-114172378
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114155391
[Test build #35451 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35451/console)
for PR 6672 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114155435
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
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6857#issuecomment-114164460
Hmm I think the Junit publish error is a known bug as we have tried to
decrease the number of tests we run per PR. (See
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-114173959
[Test build #35459 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35459/console)
for PR 6039 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-114173968
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6932#issuecomment-114180199
ok. I have merged this. Can you close this PR?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-114187161
[Test build #35460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35460/consoleFull)
for PR 6686 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-114189600
[Test build #35460 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35460/console)
for PR 6686 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r32959687
--- Diff: python/pyspark/sql/types.py ---
@@ -56,6 +56,32 @@ def __eq__(self, other):
def __ne__(self, other):
return not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-114189619
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114149805
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114150135
[Test build #951 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/951/consoleFull)
for PR 6914 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114159220
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-114164088
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-114164015
[Test build #35457 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35457/console)
for PR 6413 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6857#issuecomment-114167602
Thanks @JoshRosen -- @armisael @srowen so in this case the tests are fine
as SparkQA commented they passed in
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6857#issuecomment-114167821
@nchammas Any further comments ? Or is this good to go ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user smartkiwi opened a pull request:
https://github.com/apache/spark/pull/6936
[SPARK-8528] add applicationId property for SparkContext object in
pyspark.
Use case - we want to log applicationId (YARN in hour case) to request help
with troubleshooting from the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-114172404
Merged build started.
---
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 nssalian commented on a diff in the pull request:
https://github.com/apache/spark/pull/6924#discussion_r32958854
--- Diff: docs/running-on-yarn.md ---
@@ -7,6 +7,53 @@ Support for running on [YARN (Hadoop
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114186875
[Test build #951 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/951/consoleFull)
for PR 6914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-114186871
Merged build triggered.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/6882#issuecomment-114152570
btw, let's enable test script transform for stderr in this pr.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user karlhigley commented on a diff in the pull request:
https://github.com/apache/spark/pull/6613#discussion_r32949092
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/RandomProjection.scala ---
@@ -0,0 +1,148 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114191617
[Test build #35456 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35456/consoleFull)
for PR 6914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114191674
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3636#issuecomment-114149180
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3636#issuecomment-114149102
[Test build #35452 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35452/console)
for PR 3636 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-114153503
[Test build #35457 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35457/consoleFull)
for PR 6413 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114153450
[Test build #35456 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35456/consoleFull)
for PR 6914 at commit
Github user hhbyyh commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-114174051
@jkbradley, sent up update. Not sure if I did correctly for not adding the
metadata.
Spark-8529, 8530, 8531 created for the tasks listed.
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6810#issuecomment-114154895
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6810#issuecomment-114154839
[Test build #35450 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35450/console)
for PR 6810 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114162620
[Test build #35458 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35458/consoleFull)
for PR 6672 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6894#issuecomment-114192952
[Test build #35461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35461/consoleFull)
for PR 6894 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-114152727
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114152713
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-114152772
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114154672
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-114154621
[Test build #35449 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35449/console)
for PR 6647 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114161886
Merged build started.
---
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 hhbyyh commented on a diff in the pull request:
https://github.com/apache/spark/pull/6039#discussion_r32949758
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/MinMaxScaler.scala ---
@@ -0,0 +1,166 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user ilganeli commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r32958201
--- Diff: python/pyspark/sql/types.py ---
@@ -56,6 +56,32 @@ def __eq__(self, other):
def __ne__(self, other):
return not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114137546
[Test build #35453 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35453/consoleFull)
for PR 6935 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114137954
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6934#issuecomment-114137923
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114139615
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114139647
Merged build started.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114139657
[Test build #35455 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35455/consoleFull)
for PR 6914 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6937#issuecomment-114197085
[Test build #35462 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35462/consoleFull)
for PR 6937 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6937#issuecomment-114197164
[Test build #35462 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35462/console)
for PR 6937 at commit
Github user liancheng closed the pull request at:
https://github.com/apache/spark/pull/6932
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3881#issuecomment-114201824
Yes, also most scripts are being refactored into python so there's less of
a reason to do this. (Though the spark-daemon.sh ones are still in BASH).
Thanks.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114209774
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114209751
Merged build triggered.
---
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 nchammas commented on the pull request:
https://github.com/apache/spark/pull/6857#issuecomment-114211563
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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6911#issuecomment-114226149
This looks good to me overall. I like the idea of storing the length in
the fixed-length values section alongside the pointer to the variable-length
data. I wonder
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6910#issuecomment-114224409
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6937#issuecomment-114232296
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6923#issuecomment-114232322
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6937#issuecomment-114232278
[Test build #35475 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35475/console)
for PR 6937 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6911#discussion_r32976252
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/UnsafeRowConverter.scala
---
@@ -72,6 +70,19 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6937#issuecomment-114239576
[Test build #35477 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35477/consoleFull)
for PR 6937 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6911#issuecomment-114243182
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6686#issuecomment-114243273
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6876#issuecomment-114245985
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6876#issuecomment-114245895
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114138112
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114138077
Merged build triggered.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114138421
[Test build #35454 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35454/consoleFull)
for PR 6935 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114138899
[Test build #35454 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35454/console)
for PR 6935 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114138829
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114138905
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/3858#issuecomment-114140106
@industrial-sloth I think most of work to add a new type of DStream
includes:
1. Convert parameters from Python types to Java types
2. Convert DStream[T]
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-114137950
[Test build #35453 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35453/console)
for PR 6935 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6934#issuecomment-114137865
[Test build #35447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35447/console)
for PR 6934 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114142204
[Test build #35455 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35455/consoleFull)
for PR 6914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114142230
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
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/6923#issuecomment-114195087
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/6914#issuecomment-114195166
OK. I am merging it.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6845#issuecomment-114208486
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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6938#issuecomment-114210567
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6938#issuecomment-114211791
[Test build #35467 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35467/consoleFull)
for PR 6938 at commit
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-114211896
hi @andrewor14 - I agree with @rxin here. We should probably use the
framework's tagging mechanism, no?
---
If your project is set up for it, you can reply to
1 - 100 of 705 matches
Mail list logo
