Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4632#issuecomment-140179925
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4632#issuecomment-140179948
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 have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8457#issuecomment-140179636
LGTM. Merged into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8457
---
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 enab
Github user noel-smith commented on the pull request:
https://github.com/apache/spark/pull/8633#issuecomment-140179397
@mengxr @yu-iskw - Sounds like a plan - I'll 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 we
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8739
---
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 enab
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8682#issuecomment-140178934
We should add it as a `@property` method instead of a field. Otherwise, it
might introduce overhead with serialization.
---
If your project is set up for it, you can rep
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7842#issuecomment-140178671
@selvinsource Could you help make another pass?
---
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 pr
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8739#issuecomment-140178598
LGTM. Merging to master and branch 1.5.
---
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 doe
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8752#issuecomment-140177522
[Test build #42436 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42436/consoleFull)
for PR 8752 at commit
[`53d757a`](https://gith
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8740#discussion_r39433091
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/package-info.java ---
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (A
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8740#discussion_r39433034
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/package-info.java ---
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (A
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8740#discussion_r39433068
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/package-info.java ---
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (A
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8506#issuecomment-140177002
Hi @josiahsams,
I played a little with this and it seems like it would be rather easy to
get both rowspan and sorting working using jQuery's table sorter plugin:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8753#issuecomment-140176928
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 pr
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8740#discussion_r39433030
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/package-info.java ---
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (A
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8740#discussion_r39433039
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/package-info.java ---
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (A
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8740#discussion_r39433031
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/package-info.java ---
@@ -0,0 +1,89 @@
+/*
+ * Licensed to the Apache Software Foundation (A
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8740#issuecomment-140176618
@holdenk Please generate the JavaDoc and check the output. This is what I
got:
:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-140176392
[Test build #42433 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42433/console)
for PR 8750 at commit
[`ac49c25`](https://github.
GitHub user jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/8753
Introduce config constants object
A small refactoring to introduce a Scala object to keep
property/environment names in a single place for YARN cluster deployment first
(as I hate seeing str
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8752#issuecomment-140175794
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8752#issuecomment-140175749
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 h
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8687
---
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 enab
GitHub user jkbradley opened a pull request:
https://github.com/apache/spark/pull/8752
[SPARK-10595] [ML] [MLLIB] [DOCS] Various ML guide cleanups
Various ML guide cleanups.
* ml-guide.md: Make it easier to access the algorithm-specific guides.
* LDA user guide: EM often
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140173122
Thanks. Merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have th
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8214#issuecomment-140172099
@yanboliang Could you help review this PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-140171091
FYI, I made https://issues.apache.org/jira/browse/SPARK-10592 for
deprecating `weights`.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140170937
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140170934
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140170765
[Test build #42429 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42429/console)
for PR 8687 at commit
[`69b7d65`](https://github.
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8561#issuecomment-140169966
@holdenk Please fix style issues and remove changes to SQL. It looks good
to me otherwise.
---
If your project is set up for it, you can reply to this email and have you
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8561#discussion_r39429948
--- Diff: python/pyspark/sql/tests.py ---
@@ -830,12 +830,12 @@ def test_infer_long_type(self):
self.assertEquals(100, df1.first().f2)
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/8674#discussion_r39429841
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -192,11 +193,10 @@ object DateTimeUtils {
* Returns
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8751#issuecomment-140169168
[Test build #42435 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42435/consoleFull)
for PR 8751 at commit
[`b9577e8`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-140169045
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-140169046
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-140168836
[Test build #42428 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42428/console)
for PR 8719 at commit
[`2dc7fe2`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8751#issuecomment-140168220
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8751#issuecomment-140168248
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 have
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8751#issuecomment-140167768
LGTM pending 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 this f
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8751#issuecomment-140167644
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
enab
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8633#issuecomment-140166749
@noel-smith @yu-iskw Could you help review each other's PRs on `pyspark.ml`
`@since` versions?
* https://spark-prs.appspot.com/users/noel-smith
* https://spar
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8742#issuecomment-140165971
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8742#issuecomment-140165974
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8742#issuecomment-140165825
[Test build #42432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42432/console)
for PR 8742 at commit
[`ce6ed80`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8751#issuecomment-140164773
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 pr
GitHub user pnpritchard opened a pull request:
https://github.com/apache/spark/pull/8751
[SPARK-10573] [ML] IndexToString output schema should be StringType
Fixes bug where IndexToString output schema was DoubleType. Correct me if
I'm wrong, but it doesn't seem like the output needs
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-140163083
I'll make another pass
---
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 th
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8747#issuecomment-140162712
[Test build #42426 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42426/console)
for PR 8747 at commit
[`858f198`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140161438
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 h
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/7884#issuecomment-140161878
+1 for "coefficients"
---
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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8747#issuecomment-140162805
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140163094
[Test build #42434 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42434/consoleFull)
for PR 8688 at commit
[`ef4abaa`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8747#issuecomment-140162801
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140161471
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 have
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140161310
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 feat
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8748#issuecomment-140157619
[Test build #42427 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42427/console)
for PR 8748 at commit
[`4093255`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8748#issuecomment-140157776
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8735#discussion_r39424241
--- Diff:
core/src/main/scala/org/apache/spark/status/api/v1/OneApplicationResource.scala
---
@@ -24,7 +24,9 @@ private[v1] class OneApplicationResource(ui
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8748#issuecomment-140157778
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8735#discussion_r39424210
--- Diff:
core/src/main/scala/org/apache/spark/status/api/v1/OneApplicationResource.scala
---
@@ -24,7 +24,9 @@ private[v1] class OneApplicationResource(ui
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8674#issuecomment-140156564
Originally, we may have 0 at the field of nanoseconds?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-140148377
@viirya Thank you for the pr! However, for JSON, I am not sure we should
always write null values because the cost of encoding a null value is high. If
we always writing n
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-140148198
[Test build #42433 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42433/consoleFull)
for PR 8750 at commit
[`ac49c25`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-140147455
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8750#issuecomment-140147395
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 h
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/8750
[SPARK-10588][SQL] Saving a DataFrame containing only nulls to JSON should
work
JIRA: https://issues.apache.org/jira/browse/SPARK-10588
Currently we don't output null fields in StructType. T
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8688#issuecomment-140144174
LGTM. At first the changes to the app name seem weird, since it was nice to
have the extra information show up in the browser's title bar when looking at
the history serv
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8166#discussion_r39417765
--- Diff: python/pyspark/mllib/tests.py ---
@@ -194,6 +194,37 @@ def test_squared_distance(self):
self.assertEquals(3.0, _squared_distance(sv, arr)
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8166#discussion_r39417597
--- Diff: python/pyspark/mllib/linalg/__init__.py ---
@@ -122,6 +123,15 @@ def _format_float_list(l):
return [_format_float(x) for x in l]
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8362#issuecomment-140141999
@MLnick This one will replace the existing implementation. For now, we will
do conversion as shown at
https://github.com/apache/spark/pull/8362/files#diff-78b9b210b8cee72e
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/8669#discussion_r39416439
--- Diff: bin/beeline ---
@@ -23,8 +23,29 @@
# Enter posix mode for bash
set -o posix
+realpath () {
--- End diff --
Yes, th
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8705#issuecomment-140138557
For the issue of `NaN`, looks like there is something wrong because we want
to return true when compare two `NaN`.
---
If your project is set up for it, you can reply to
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140137297
LGTM. Will merge to master once it passes 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8742#issuecomment-140136499
[Test build #42432 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42432/consoleFull)
for PR 8742 at commit
[`ce6ed80`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-140136364
[Test build #42431 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42431/consoleFull)
for PR 7971 at commit
[`25494f2`](https://gith
GitHub user yjshen reopened a pull request:
https://github.com/apache/spark/pull/8742
[SPARK-10539][SQL]Fix set optimization by eliminate empty project list push
down
Push down empty project list through `Intersect` or `Except` would make all
the rows in both child to empty row, wh
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8742#issuecomment-140135612
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8742#issuecomment-140135561
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 h
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8705#issuecomment-140134401
Filed https://issues.apache.org/jira/browse/SPARK-10591 to track this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-140134115
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7971#issuecomment-140134082
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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8749#issuecomment-140134071
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 pr
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8749#issuecomment-140134096
That seems reasonable, as long as its semantics are understood: stopping
has begun, not necessarily completed. I'd like at least one other +1 before
proceeding just becau
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8705#issuecomment-140133705
Found two possible sources of flakiness:
1. For double and float, `NaN == NaN` is always `false`
2. `checkAnswer` doesn't handle `Map[K, V]` properly. For e
GitHub user kmadhugit opened a pull request:
https://github.com/apache/spark/pull/8749
[SPARK-10458] [Spark Core] Added isStopped() method in SparkContext
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ibmsoe/spark SPARK-10458
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6457#issuecomment-140130053
[Test build #42430 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42430/consoleFull)
for PR 6457 at commit
[`56b5beb`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6457#issuecomment-140129638
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6457#issuecomment-140129575
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140124239
[Test build #42429 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42429/consoleFull)
for PR 8687 at commit
[`69b7d65`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140122699
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8687#issuecomment-140122746
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-140122145
[Test build #42428 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42428/consoleFull)
for PR 8719 at commit
[`2dc7fe2`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8748#issuecomment-140122195
[Test build #42427 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42427/consoleFull)
for PR 8748 at commit
[`4093255`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-140119956
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 have
GitHub user steveloughran opened a pull request:
https://github.com/apache/spark/pull/8748
Stevel/patches/spark 8789 sql query suite table drop
Updated version of SPARK-8789 which switches to `withSqlContext` for the
operations which change the sql context.
Note that `withT
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8719#issuecomment-140119911
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 h
401 - 500 of 660 matches
Mail list logo
