Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-5274
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20321/consoleFull)
for PR 1983 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-5663
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20322/consoleFull)
for PR 2250 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-6122
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20327/consoleFull)
for PR 2358 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-6169
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20327/consoleFull)
for PR 2358 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2219#issuecomment-6421
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20325/consoleFull)
for PR 2219 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-6582
Hey @pwendell, I can remove the commit once you confirm it works.
---
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 pull request:
https://github.com/apache/spark/pull/1977#issuecomment-6598
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20328/consoleFull)
for PR 1977 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2368#issuecomment-6637
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
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2357#issuecomment-6738
you are right about that, but we are forking it because we want an install
plugin modified. If it was possible to run a plugin just before install and
install plugin
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2368#issuecomment-6842
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20329/consoleFull)
for PR 2368 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2333#issuecomment-7935
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20326/consoleFull)
for PR 2333 at commit
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528496
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -181,11 +182,25 @@ class SqlParser extends StandardTokenParsers
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528493
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -181,11 +182,25 @@ class SqlParser extends StandardTokenParsers
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528508
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -305,6 +305,8 @@ private[sql] abstract class SparkStrategies
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528600
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/CachedTableSuite.scala ---
@@ -119,4 +119,16 @@ class CachedTableSuite extends QueryTest {
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528595
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -166,3 +166,22 @@ case class DescribeCommand(child: SparkPlan,
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528605
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -214,6 +214,7 @@ private[hive] object HiveQl {
*/
def
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528625
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -1097,7 +1109,7 @@ private[hive] object HiveQl {
case
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528618
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -229,11 +230,17 @@ private[hive] object HiveQl {
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2390#discussion_r17528644
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -127,6 +127,7 @@ class SqlParser extends StandardTokenParsers
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-8998
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20324/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2357#issuecomment-9135
I am anyway trying more options to not need to modify maven-install-pluing.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17528900
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -181,6 +182,12 @@ class SqlParser extends StandardTokenParsers
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17528911
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/SqlParser.scala ---
@@ -181,6 +182,12 @@ class SqlParser extends StandardTokenParsers
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17528919
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -166,3 +166,24 @@ case class DescribeCommand(child: SparkPlan,
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17528937
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -166,3 +166,24 @@ case class DescribeCommand(child: SparkPlan,
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17528957
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/CachedTableSuite.scala ---
@@ -119,4 +119,20 @@ class CachedTableSuite extends QueryTest {
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17528949
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -166,3 +166,24 @@ case class DescribeCommand(child: SparkPlan,
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17529002
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -214,6 +214,7 @@ private[hive] object HiveQl {
*/
def
Github user staple commented on a diff in the pull request:
https://github.com/apache/spark/pull/2385#discussion_r17528982
--- Diff: python/pyspark/traceback_utils.py ---
@@ -0,0 +1,80 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+#
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17529035
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -233,7 +234,7 @@ private[hive] object HiveQl {
} else if
Github user ravipesala commented on a diff in the pull request:
https://github.com/apache/spark/pull/2381#discussion_r17529073
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -243,14 +244,12 @@ private[hive] object HiveQl {
} else if
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1847#issuecomment-55560383
I will close this PR, since most of work was done in #1846 #1962, and
native command support for `EXPLAIN` probably not necessary, even Hive doesn't
support it.
Github user chenghao-intel closed the pull request at:
https://github.com/apache/spark/pull/1847
---
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 pull request:
https://github.com/apache/spark/pull/1977#issuecomment-55560776
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20328/consoleFull)
for PR 1977 at commit
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-55560892
A flagged character looks like this:
```=
Running Scala style checks
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/2392
[SPARK-3527] [SQL] Strip the string message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chenghao-intel/spark trim
Alternatively you
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-55560989
Yeah Thanks, @ash211 I will get rid of that commit.
---
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 pull request:
https://github.com/apache/spark/pull/2392#issuecomment-55561297
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20330/consoleFull)
for PR 2392 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-55561642
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20331/consoleFull)
for PR 2358 at commit
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/2393
[SPARK-3529] [SQL] Delete the temp files after test exit
There are lots of temporal files created by TestHive under the /tmp by
default, which may cause potential performance issue for
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2386#discussion_r17530408
--- Diff: bin/spark-shell ---
@@ -29,7 +29,7 @@ esac
set -o posix
## Global script variables
-FWDIR=$(cd `dirname $0`/..; pwd)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2393#issuecomment-55563405
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20332/consoleFull)
for PR 2393 at commit
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2386#discussion_r17530450
--- Diff: bin/spark-shell ---
@@ -29,7 +29,7 @@ esac
set -o posix
## Global script variables
-FWDIR=$(cd `dirname $0`/..; pwd)
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2387#issuecomment-55563583
This is also a duplicate, of #2301.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/449#discussion_r17530603
--- Diff: bin/run-example ---
@@ -21,18 +21,25 @@ SCALA_VERSION=2.10
FWDIR=$(cd `dirname $0`/..; pwd)
export SPARK_HOME=$FWDIR
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2368#issuecomment-55564638
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20329/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user epahomov commented on the pull request:
https://github.com/apache/spark/pull/2371#issuecomment-55565128
Closed, because currently there is similar work in Databricks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2382#discussion_r17531198
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/unresolved.scala
---
@@ -98,12 +98,12 @@ case class Star(
GitHub user epahomov opened a pull request:
https://github.com/apache/spark/pull/2394
[Spark-3525] Adding gradient boosting
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/epahomov/spark SPARK-3525
Alternatively you can review
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2382#discussion_r17531193
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/package.scala
---
@@ -22,4 +22,9 @@ package
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2358#issuecomment-55565526
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20331/consoleFull)
for PR 2358 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2382#discussion_r17531262
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala
---
@@ -105,7 +119,9 @@ abstract class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2394#issuecomment-55565637
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/2395
[Minor]ignore all config files in conf
Some config files in ```conf``` should ignore, such as
conf/fairscheduler.xml
conf/hive-log4j.properties
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2395#issuecomment-55566939
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/2396
[SPARK-3531][SQL]select null from table would throw a MatchError
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/adrian-wang/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2392#issuecomment-55568137
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20330/consoleFull)
for PR 2392 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2396#issuecomment-55568780
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20333/consoleFull)
for PR 2396 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2393#issuecomment-55570548
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20332/consoleFull)
for PR 2393 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2357#issuecomment-55570721
- If you bind a plugin to `install` phase and declare it before
`maven-install-plugin`, will it happen to respect the ordering?
- This is arguably something that can
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2393#discussion_r17533627
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/TestHive.scala
---
@@ -41,7 +49,27 @@ import org.apache.spark.sql.SQLConf
import
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2391#issuecomment-55571126
Can you explain this patch? What problem does it solve and why? There is no
JIRA here either.
---
If your project is set up for it, you can reply to this email and have
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2357#issuecomment-55571483
Hi @srowen, like I said. We can run a plugin before maven install - no
question about that. But since maven install gets a copy of STATE(somehoe via
guice). Altering
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2357#issuecomment-55572928
I see, I thought you mentioned above that running a plugin before `install`
would work. It sounds like there is some internal state of the plugin you need
to modify, OK.
GitHub user ravipesala opened a pull request:
https://github.com/apache/spark/pull/2397
[SPARK-2594][SQL] Add CACHE TABLE name AS SELECT ...
This feature allows user to add cache table from the select query.
Example : ADD CACHE TABLE AS SELECT * FROM TEST_TABLE.
Spark takes
Github user ravipesala commented on the pull request:
https://github.com/apache/spark/pull/2381#issuecomment-55574730
As there is a confusion in rebasing, I have created a new pull request
https://github.com/apache/spark/pull/2397 rebased with master and also fixed
the review
Github user ravipesala commented on the pull request:
https://github.com/apache/spark/pull/2390#issuecomment-55574756
As there is a confusion in rebasing, I have created a new pull request
https://github.com/apache/spark/pull/2397 rebased with master and also fixed
the review
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2397#issuecomment-55574757
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2396#issuecomment-55575850
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20333/consoleFull)
for PR 2396 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55576959
I have changed the way to fix the problem here, keeping most of the
original logics. @marmbrus
---
If your project is set up for it, you can reply to this email and
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55577018
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55577211
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20334/consoleFull)
for PR 2355 at commit
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2365#issuecomment-55582578
thanks, +1, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55582984
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20334/consoleFull)
for PR 2355 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-55586887
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20335/consoleFull)
for PR 2388 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2320#issuecomment-55588750
yes that is how it works in standalone mode and it will. The master,
workers, and all the applications/clients/drivers need to have the same shared
secret. It will
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55590580
Sorry for the missings here...
---
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 mattf commented on a diff in the pull request:
https://github.com/apache/spark/pull/2383#discussion_r17541864
--- Diff: python/pyspark/tests.py ---
@@ -586,6 +586,17 @@ def test_repartitionAndSortWithinPartitions(self):
self.assertEquals(partitions[0], [(0,
Github user mattf commented on a diff in the pull request:
https://github.com/apache/spark/pull/2383#discussion_r17542165
--- Diff: python/pyspark/rdd.py ---
@@ -353,7 +353,7 @@ def func(iterator):
return ifilter(f, iterator)
return
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2283#issuecomment-55592767
+1 looks good. Thanks @sarutak
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/2283
---
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 BigCrunsh opened a pull request:
https://github.com/apache/spark/pull/2398
[SPARK-3396][MLLIB] Use SquaredL2Updater in LogisticRegressionWithSGD
SimpleUpdater ignores the regularizer, which leads to an unregularized
LogReg. To enable the common L2 regularizer (and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2383#issuecomment-55594346
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20336/consoleFull)
for PR 2383 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2231#issuecomment-55594378
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20337/consoleFull)
for PR 2231 at commit
Github user BigCrunsh closed the pull request at:
https://github.com/apache/spark/pull/2231
---
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 BigCrunsh commented on the pull request:
https://github.com/apache/spark/pull/2231#issuecomment-55594501
Changed target to master (https://github.com/apache/spark/pull/2398)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55594998
@chenghao-intel This is not so complex since it is not GenericUDF, but
simple UDF with limited types. So we do not need to call those here.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2398#issuecomment-55595028
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20338/consoleFull)
for PR 2398 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2355#issuecomment-55595044
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20339/consoleFull)
for PR 2355 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2388#issuecomment-55595533
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20335/consoleFull)
for PR 2388 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2396#issuecomment-55595820
This is according to how Hive handle immediate null value in queries.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2014#issuecomment-55598514
@andrewor14 @nchammas @pwendell Humble ping on this one, I think it's good
to go, and probably helps head off some build questions going forward.
---
If your project is
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2313#issuecomment-55601210
thanks @erikerlandson. @davies @JoshRosen how would you guys like to
proceed?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r17546110
--- Diff: docs/building-spark.md ---
@@ -159,4 +160,13 @@ then ship it over to the cluster. We are investigating
the exact cause for this.
The
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r17546414
--- Diff: docs/building-spark.md ---
@@ -159,4 +160,13 @@ then ship it over to the cluster. We are investigating
the exact cause for this.
The
Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/2014#discussion_r17547220
--- Diff: docs/building-spark.md ---
@@ -159,4 +160,13 @@ then ship it over to the cluster. We are investigating
the exact cause for this.
The
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2383#issuecomment-55604353
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20336/consoleFull)
for PR 2383 at commit
Github user aaronjosephs commented on the pull request:
https://github.com/apache/spark/pull/1381#issuecomment-55604431
@JoshRosen this isn't necessarily specified on the ticket but it's related.
Since most of the time something will be range partitioned because you called
sortByKey
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2398#issuecomment-55604710
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20338/consoleFull)
for PR 2398 at commit
1 - 100 of 345 matches
Mail list logo
