Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6430#issuecomment-107318741
Hi all, I just updated the code according to your comments, please help to
review, thanks a lot. There's two opening questions I didn't address yet:
1. Do we
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6548#issuecomment-107318861
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/6548#issuecomment-107318918
[Test build #33880 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33880/consoleFull)
for PR 6548 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6548#issuecomment-107318873
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 jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/6430#discussion_r31402037
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -261,14 +270,19 @@ private[spark] class ExecutorAllocationManager(
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/6430#discussion_r31402047
--- Diff:
core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala ---
@@ -261,14 +270,19 @@ private[spark] class ExecutorAllocationManager(
GitHub user tarekauel opened a pull request:
https://github.com/apache/spark/pull/6549
[SPARK-7966][GraphX] Implementation of Spreading Activation algorithm
I implemented the Spreading Activation algorithm and would love to get your
feedback
You can merge this pull request into a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6549#issuecomment-107319654
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/6430#issuecomment-107320286
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/6430#issuecomment-107320335
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/6430#issuecomment-107320528
[Test build #33881 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33881/consoleFull)
for PR 6430 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6547#discussion_r31402480
--- Diff:
sql/hive-thriftserver/src/test/scala/org/apache/spark/sql/hive/thriftserver/HiveThriftServer2Suites.scala
---
@@ -29,6 +27,8 @@ import
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6537#issuecomment-107322383
[Test build #33874 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33874/consoleFull)
for PR 6537 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6537#issuecomment-107322393
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6351#issuecomment-107323110
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/6351#issuecomment-107323104
[Test build #33875 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33875/consoleFull)
for PR 6351 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6548
---
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 pull request:
https://github.com/apache/spark/pull/6361#issuecomment-107331992
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/6361#issuecomment-107331980
[Test build #33879 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33879/consoleFull)
for PR 6361 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6547#issuecomment-107332113
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/6547#issuecomment-107332108
[Test build #33876 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33876/consoleFull)
for PR 6547 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-107334960
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/6405#issuecomment-107334830
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/6405#issuecomment-107336115
[Test build #33882 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33882/consoleFull)
for PR 6405 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6538#issuecomment-107407349
[Test build #33887 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33887/consoleFull)
for PR 6538 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6514#issuecomment-107430364
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6551#discussion_r31416746
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -47,9 +47,14 @@ object HiveTypeCoercion {
Github user animeshbaranawal closed the pull request at:
https://github.com/apache/spark/pull/6552
---
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 animeshbaranawal commented on the pull request:
https://github.com/apache/spark/pull/6552#issuecomment-107411465
Thanks for that suggestion... I will close this request then!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user animeshbaranawal opened a pull request:
https://github.com/apache/spark/pull/6553
[SPARK-7980] [SQL] Support SQLContext.range(end)
Used previous defined range(start,end) to define range(end)
You can merge this pull request into a Git repository by running:
$ git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6554#issuecomment-107422132
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/6546#issuecomment-107422149
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/6546#issuecomment-107422137
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/6546#issuecomment-107422417
[Test build #33888 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33888/consoleFull)
for PR 6546 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6546#issuecomment-107419985
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/6546#issuecomment-107419976
**[Test build #33885 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33885/consoleFull)**
for PR 6546 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107428549
[Test build #33886 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33886/consoleFull)
for PR 6409 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107428565
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/6514#issuecomment-107430413
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/6514#issuecomment-107430622
[Test build #33889 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33889/consoleFull)
for PR 6514 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/6551#issuecomment-107409147
`findTightestCommonType` is also used in Rule `WidenTypes` which is run
before `PromoteStrings`, and your change will break some special logic for
binary comparison
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6546#issuecomment-107421913
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 WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/6545#issuecomment-107430955
Hey Sean, what we wanna fix is the load once, show them forever issue.
That is to say, when user click a link on history page, the provider will load
an
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6552#discussion_r31418069
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -701,6 +701,21 @@ class SQLContext(@transient val sparkContext:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6553#issuecomment-107415516
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 jeanlyn commented on the pull request:
https://github.com/apache/spark/pull/5876#issuecomment-107415482
I set the metastore to `0.12.0` by follow steps ,but get classnotdef
exception:
* I chang the `spark.sql.hive.metastore.version` in `spark-defaults.conf`
to
GitHub user lucarosellini opened a pull request:
https://github.com/apache/spark/pull/6554
[SPARK-4782] Add inferSchema support for RDD[Map[String, Any]]
In this PR we added a generic inferSchema method to allow schema infer for
an RDD of a generic type T for which the user
Github user dusenberrymw commented on the pull request:
https://github.com/apache/spark/pull/6514#issuecomment-107429338
Updated!
---
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 pull request:
https://github.com/apache/spark/pull/6405#issuecomment-107342822
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/6548#issuecomment-107342934
[Test build #33880 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33880/consoleFull)
for PR 6548 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-107342852
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/6550#issuecomment-107345671
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/6550#issuecomment-107345867
[Test build #33884 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33884/consoleFull)
for PR 6550 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6550#issuecomment-107345653
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/6430#issuecomment-107353994
[Test build #33881 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33881/consoleFull)
for PR 6430 at commit
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/2994#issuecomment-107380655
@tdas
I was thinking we should maybe document this use case in [the checkpointing
section of the streaming programming
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6538#issuecomment-107406673
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6538#issuecomment-107406712
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 have this
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6519#discussion_r31405070
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -210,13 +210,25 @@ case class EqualNullSafe(left:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6552#issuecomment-107392675
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6544#issuecomment-107380177
That's fine. This does not warrant a JIRA.
(PS why do your PRs have a huge merge history? you'd normally just branch
from an updated master right?)
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6546#issuecomment-107382508
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/6546#issuecomment-107382587
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 OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/6551#issuecomment-107399872
@chenghao-intel Could u please review this?
---
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 OopsOutOfMemory opened a pull request:
https://github.com/apache/spark/pull/6551
[SPARK-8010][SQL]Promote numeric types to string type as implicit
conversion in HiveTypeCoercion
1. Given a query
`select coalesce(null, 1, '1') from dual` will cause exception:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6550#issuecomment-107383206
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/6550#issuecomment-107383190
[Test build #33884 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33884/consoleFull)
for PR 6550 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107399589
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/6430#issuecomment-107342481
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/6430#issuecomment-107354037
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6546#issuecomment-107379861
@zsxwing are these things you identify actually causing test failures for
you or in Jenkins or is this theoretical?
---
If your project is set up for it, you can reply
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6545#issuecomment-107381570
Can you explain this more? what does this accomplish that isn't
accomplished by refreshing the page? and unless the page is refreshed I would
not expect an update.
GitHub user animeshbaranawal opened a pull request:
https://github.com/apache/spark/pull/6552
[SPARK-7980] [SQL] Support SQLContext.range(end)
Created an API range(end:Long) which generates dataframe containing entries
from 0 to end-1.
Added three tests accordingly in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6548#issuecomment-107342947
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/6405#issuecomment-107343141
[Test build #33883 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33883/consoleFull)
for PR 6405 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6546#issuecomment-107381194
@srowen These two failures happened in my PR #6457. I fixed them in #6457
to pass Jenkins. But I think they are not a part of #6457 and it's better to
fix them in a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107399575
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/6409#issuecomment-107399653
[Test build #33886 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33886/consoleFull)
for PR 6409 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6430#issuecomment-107342472
[Test build #33878 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33878/consoleFull)
for PR 6430 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6416#issuecomment-107342342
Can you give an example of what your returned DataFrame looks like?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6550#issuecomment-107345032
@andrewor14 could you take a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/6405#discussion_r31406630
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -264,6 +264,10 @@ object NullPropagation extends
Github user zhichao-li commented on a diff in the pull request:
https://github.com/apache/spark/pull/6404#discussion_r31406553
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/SQLQuerySuite.scala
---
@@ -629,12 +633,24 @@ class SQLQuerySuite extends QueryTest
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-107382964
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/6546#issuecomment-107382981
[Test build #33885 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33885/consoleFull)
for PR 6546 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-107382949
[Test build #33882 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33882/consoleFull)
for PR 6405 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/6550
[SPARK-8001][Core]Make AsynchronousListenerBus.waitUntilEmpty throw
TimeoutException if timeout
Some places forget to call `assert` to check the return value of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6405#issuecomment-107387510
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/6405#issuecomment-107387487
[Test build #33883 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33883/consoleFull)
for PR 6405 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/6416#issuecomment-107348123
For input DataFrame with a column name A:
A
1
10
5
10
8
The returned DataFrame has two columns A
Github user zhichao-li commented on a diff in the pull request:
https://github.com/apache/spark/pull/6404#discussion_r31406980
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/ScriptTransformation.scala
---
@@ -58,6 +59,7 @@ case class ScriptTransformation(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6551#issuecomment-107382503
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 tbertelsen commented on the pull request:
https://github.com/apache/spark/pull/6454#issuecomment-107391759
@viirya Sadly I don't have access to our compute cluster for the next
couple of weeks so I can try it out right now.
---
If your project is set up for it, you can
Github user Sephiroth-Lin commented on the pull request:
https://github.com/apache/spark/pull/6409#issuecomment-107399469
Jenkins, 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
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6554#issuecomment-107572172
I don't know anything about this feature or patch, but as an outside
observer I _can_ say that this needs tests or at least _a_ test to make sure
that this feature
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/6519#issuecomment-107583103
Hive's UDAF max and min support the comparison on named_struct (ref. the
links in JIRA). I think it should be reasonable to support comparison on struct
type by
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6537#issuecomment-107586402
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/6519#issuecomment-107586393
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/6519#issuecomment-107586359
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/6537#issuecomment-107586352
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
1 - 100 of 665 matches
Mail list logo
