Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1761#issuecomment-51020215
In general, I'm wary of merging this type of very-small-scale code cleanup;
I don't think this makes the code any easier to understand and it may cause
merge conflicts
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1542#issuecomment-51020347
Since this same locking pattern occurs at several places in the code, I
think it might make sense to abstract it behind a function or macro, which
would give us a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-51020440
QA results for PR 1719:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-51020596
This looks okay, but I still wonder whether there's a simpler approach.
Have you looked at how [dill](https://github.com/uqfoundation/dill) handles
namedtuples?
---
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1758#issuecomment-51020658
Jenkins, 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-51020851
It's easy to extend pickle to support namedtuple, couldpickle and dill have
done in this way, but they are slow. We want to use cPickle for dataset, it
should be fast by
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1758#issuecomment-51020991
QA tests have started for PR 1758. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17845/consoleFull
---
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-51021254
Jenkins, 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
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/1760#issuecomment-51021277
@chenghao-intel is these files all right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-51021399
Here's another (contrived) example that breaks:
```python
from collections import namedtuple as nt
from pyspark import SparkContext
from
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-51021526
QA tests have started for PR 1719. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17846/consoleFull
---
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/996#discussion_r15741984
--- Diff: assembly/pom.xml ---
@@ -26,7 +26,7 @@
/parent
groupIdorg.apache.spark/groupId
- artifactIdspark-assembly_2.10/artifactId
Github user javadba commented on the pull request:
https://github.com/apache/spark/pull/1542#issuecomment-51022369
Thanks for commenting Josh. I will see about putting together something on
this including solid testcases. ETA later in the coming week.
---
If your project is set up
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-51022848
Yes, it's easy to break it.
Having an solution working in 99% cases is better than no solutions, or
much slower solution working 100% cases.
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-51023016
QA results for PR 1719:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-51023029
This feature is not blocker, because we prefer use Row() instead of
namedtuple to do inferSchema().
If user really want to use namedtuple or customized class in
Github user avulanov commented on the pull request:
https://github.com/apache/spark/pull/1484#issuecomment-51023586
@mengxr Could you review or comment this? 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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-51023600
LGTM. Merged into both master and branch-1.1. @Ishiihara Thanks a lot for
implementing word2vec! Please help improve its performance during the QA
period. One task left
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/476#discussion_r15742427
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/MLUtils.scala ---
@@ -233,4 +235,60 @@ object MLUtils {
}
sqDist
}
+
GitHub user kayousterhout opened a pull request:
https://github.com/apache/spark/pull/1762
Remove support for waiting for executors in standalone mode.
Current code waits until some minimum fraction of expected executors
have registered before beginning scheduling. The current
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1462#issuecomment-51024346
@pwendell I created https://github.com/apache/spark/pull/1762 for your
judgment of what the right thing to do here is!
---
If your project is set up for it, you
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/1762#discussion_r15742607
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
---
@@ -0,0 +1,63 @@
+/*
+ * Licensed to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1719
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1484#issuecomment-51024568
Sure. We had some transformers implemented under `mllib.feature`, similar
to sk-learn's approach. For feature selection, we can follow the same approach
if we view
GitHub user luluorta opened a pull request:
https://github.com/apache/spark/pull/1763
fix GraphX EdgeRDD zipPartitions
If the users set âspark.default.parallelismâ and the value is different
with the EdgeRDD partition number, GraphX jobs will throw:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1763#issuecomment-51024735
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1715#issuecomment-51024718
@liancheng why not just have the jars listed on the classpath in the order
they are given to us? This is also how classpaths work in general, when I run a
java command,
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1715#issuecomment-51024798
@andrewor14 I still don't understand how this is different. Basically, the
JVM works such that you put a set of jars in order (indicating precedence) and
then you can
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/1481#discussion_r15742765
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -29,7 +29,7 @@ import akka.actor.{ActorSystem, Cancellable, Props}
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1623#issuecomment-51024991
I found another technique that may be more robust to `namedtuple` being
accessible under different names. We can replace `namedtuple`'s code object at
runtime in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1719#issuecomment-51025157
QA results for PR 1719:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1760#issuecomment-51025307
Jenkins, 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
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/1481#issuecomment-51025499
Updated patch addresses @pwendell and @kayousterhout 's comments and adds
tests.
---
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/1481#issuecomment-51025769
QA tests have started for PR 1481. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17848/consoleFull
---
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/996#discussion_r15743162
--- Diff: assembly/pom.xml ---
@@ -26,7 +26,7 @@
/parent
groupIdorg.apache.spark/groupId
-
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1462#issuecomment-51026034
Okay let me run it by some more people tomorrow and figure it out.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/1764#discussion_r15743214
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/dsl/package.scala ---
@@ -266,7 +266,8 @@ package object dsl {
object plans
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/1764
[SPARK-2824/2825][SQL] Work towards separating data location from format
Currently, there is a fundamental assumption in SparkSQL that a Parquet
table is stored at a certain Hadoop path and
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/1764#discussion_r15743237
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/physical/TableFormat.scala
---
@@ -0,0 +1,53 @@
+/*
+ * Licensed to the
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1481#issuecomment-51026321
Cool - thanks Sandy. Let's see if tests pass. Can likely merge this
tomorrow and fix any remaining issues (if they exist).
---
If your project is set up for it, you
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/1764#discussion_r15743336
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetTypes.scala ---
@@ -353,15 +356,14 @@ private[parquet] object ParquetTypesConverter
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1764#issuecomment-51026425
QA tests have started for PR 1764. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17849/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1764#issuecomment-51026471
QA results for PR 1764:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1764#issuecomment-51026733
QA tests have started for PR 1764. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17850/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1764#issuecomment-51026778
QA results for PR 1764:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brclass
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1754#issuecomment-51027051
I think this is an intermediate YARN version that is different from both
the yarn-alpha and yarn-stable API's. @witgo what if you apply the patch here -
does it work?
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1754#issuecomment-51028168
This PR makes sbt' s behavior is consistent with [building-with-maven.md]
(https://github.com/apache/spark/blob/master/docs/building-with-maven.md)
description.
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/714#issuecomment-51029448
hey @andrewor14 ï¼ i can not see FAILED unit tests info, so i do not know
how to resolve it. can you help me
---
If your project is set up for it, you can reply to this
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/1752#issuecomment-51030127
@pwendell Ah, so that's what's causing it. Yes, fix forward by all means,
but can this be disabled until that time? it looks like about half or more of
all test runs are
GitHub user chenghao-intel opened a pull request:
https://github.com/apache/spark/pull/1765
[SQL] [SPARK-2826] Reduce the memory copy while building the hashmap for
HashOuterJoin
This is a follow up for #1147 , this PR will improve the performance about
10% - 15% in my local
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1765#issuecomment-51030910
QA tests have started for PR 1765. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17851/consoleFull
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1754#discussion_r15745620
--- Diff: project/SparkBuild.scala ---
@@ -71,7 +71,7 @@ object SparkBuild extends PomBuild {
}
Properties.envOrNone(SPARK_HADOOP_VERSION)
GitHub user larryxiao opened a pull request:
https://github.com/apache/spark/pull/1766
[SPARK-1986][GraphX]move lib.Analytics to org.apache.spark.examples
to support ~/spark/bin/run-example GraphXAnalytics triangles
/soc-LiveJournal1.txt --numEPart=256
You can merge this pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1766#issuecomment-51032872
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 avulanov commented on the pull request:
https://github.com/apache/spark/pull/1484#issuecomment-51033011
@mengxr
1. Do I understand correct, that you propose that `fit(dataset:
RDD[LabeledPoint])` should compute feature scores according to the feature
selection
GitHub user luluorta opened a pull request:
https://github.com/apache/spark/pull/1767
[SPARK-2827][GraphX]Add degree distribution operators in GraphOps for GraphX
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/luluorta/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1767#issuecomment-51033669
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/1754#issuecomment-51033818
@pwendell #151 compilation fails.
There seems to be infinite loop:
` SPARK_HADOOP_VERSION=2.0.0-cdh4.5.0 SPARK_YARN=true SPARK_HIVE=true
sbt/sbt clean
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1754#issuecomment-51034387
We need to explicitly pointed out that spark does not support the version
`2.0.x` and `2.1.x` of yarn ?
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-51037911
QA tests have started for PR 1616. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17852/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1765#issuecomment-51039744
QA results for PR 1765:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-51044768
QA results for PR 1616:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1722#discussion_r15750212
--- Diff:
core/src/main/scala/org/apache/spark/serializer/JavaSerializer.scala ---
@@ -35,16 +35,15 @@ private[spark] class JavaSerializationStream(out:
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1722#issuecomment-51047651
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/1754#issuecomment-51048750
@witgo I don't think #151 is to be committed, if I understand correctly.
It's not 100% clear which versions of YARN 2.0.x actually work with
`yarn-alpha`, and which if
Github user li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-51051752
@JoshRosen added comment.
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/1715#issuecomment-51055752
@pwendell OK, the `java -firstCpElement` example really convinced me :) I
used to think asking users to care about the order of the jars is a little too
much, but
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1750#issuecomment-51064528
QA tests have started for PR 1750. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17853/consoleFull
---
Github user javadba commented on the pull request:
https://github.com/apache/spark/pull/1586#issuecomment-51065193
Hi,
For some reason the CORE module testing has ballooned in overall testing
time: it took over 7.5 hours to run. There was one timeout error out of 736
tests -
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-51068459
QA tests have started for PR 1323. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17854/consoleFull
---
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-51069490
Related work #1330
---
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/1330#issuecomment-51070559
QA tests have started for PR 1330. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17855/consoleFull
---
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1269#discussion_r15759585
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/topicmodeling/utils/serialization/TObjectIntHashMapSerializer.scala
---
@@ -0,0 +1,51 @@
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1269#discussion_r15759818
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/clustering/topicmodeling/topicmodels/RobustPLSASuite.scala
---
@@ -0,0 +1,40 @@
+/*
+ * Licensed
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/1760#issuecomment-51072215
what's wrong with 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
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/1490#issuecomment-51072948
Thanks for your back up @JoshRosen .
---
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 pull request:
https://github.com/apache/spark/pull/1750#issuecomment-51075115
QA results for PR 1750:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brcase class
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1760#issuecomment-51075309
Jenkins, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1323#issuecomment-51076281
QA results for PR 1323:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1330#issuecomment-51078602
QA results for PR 1330:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-51081881
Thanks for commenting. I now realize that my concern about advisory
locking was a little misguided, since only cooperating Spark processes will be
coordinating
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1760#issuecomment-51083724
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-51085554
This seems like an alright fix and I'd like to get it into a release, but
I'm concerned that this doesn't correctly handle every possible feature of
`fetchFile`.
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1702#issuecomment-51085913
Jenkins, 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1702#issuecomment-51086273
QA tests have started for PR 1702. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17856/consoleFull
---
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1484#issuecomment-51086836
@avulanov I have the same concern about calling `transform` before `fit`.
There are two options: 1) throw an error, 2) fit on the same dataset and then
transform
Github user chutium commented on a diff in the pull request:
https://github.com/apache/spark/pull/1346#discussion_r15766362
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -89,6 +88,44 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/1744#issuecomment-51087364
@rxin @pwendell This PR is ready for review.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1758#issuecomment-51087933
Jenkins, retest this please @JoshRosen it appears something timed out or
failed during the tests
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1758#issuecomment-51088288
QA tests have started for PR 1758. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17857/consoleFull
---
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1715#issuecomment-51089001
@pwendell How about for python files? What if I have one.py and two.py that
reference each other, and I want spark-submit to run the main method of one.py
but not
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/1346#discussion_r15767384
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -89,6 +88,44 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1309#issuecomment-51089309
QA tests have started for PR 1309. This patch DID NOT merge cleanly!
brView progress:
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1715#issuecomment-51089761
@andrewor14 I believe Patrick means:
1. For Scala/Java applications, the primary jar should appear as the 1st
entry of `--jars`
1. For Python applications,
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1758#discussion_r15768094
--- Diff:
core/src/main/scala/org/apache/spark/network/ConnectionManager.scala ---
@@ -41,16 +42,26 @@ import org.apache.spark.util.{SystemClock, Utils}
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1715#issuecomment-51090902
Hm, I see. Even then we still need some kind of separator right? I thought
the whole point of handling primary resources differently here (either under
`--primary` or
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1702#issuecomment-51091836
QA results for PR 1702:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user avati commented on the pull request:
https://github.com/apache/spark/pull/1702#issuecomment-51092475
It is not clear how the failure is related to 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.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1309#issuecomment-51092478
QA tests have started for PR 1309. This patch DID NOT merge cleanly!
brView progress:
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/1309#discussion_r15769145
--- Diff: core/src/main/scala/org/apache/spark/scheduler/TaskInfo.scala ---
@@ -42,6 +44,13 @@ class TaskInfo(
var gettingResultTime: Long = 0
1 - 100 of 405 matches
Mail list logo
