Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7410
---
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 zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9741#discussion_r45146496
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingListenerSuite.scala
---
@@ -320,3 +340,17 @@ class FailureReasonsCollector extends
St
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157562173
**[Test build #46132 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46132/consoleFull)**
for PR 9741 at commit
[`e0c6163`](https://gith
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9301#issuecomment-157562248
It was added to provide docker support for launching Spark on Mesos,
remember?: #3074
---
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/9782#issuecomment-157562052
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9782#issuecomment-157562049
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/9783#issuecomment-157562122
**[Test build #46131 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46131/consoleFull)**
for PR 9783 at commit
[`6a10080`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9782#issuecomment-157561951
[Test build #46123 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46123/console)
for PR 9782 at commit
[`0e40fc8`](https://github.
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9742#issuecomment-157561914
All right. I am merging to master and 1.6. Thanks @jerryshao for all the
effort, and @zsxwing for getting this ready.
---
If your project is set up for it, you can reply
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/9687#issuecomment-157561940
Several things to mention.
Firstly, I wonder if it is okay to put `extractSourceRDDToDataFrame` at
`QueryTest`. I did not put but I think the `extractSourceR
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9782#issuecomment-157561666
Merging this. thanks for fixing this @zsxwing
---
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 proje
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9783
[SPARK-10186][SQL][follow-up] simplify test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark postgre
Alternatively you can rev
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157560994
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 brkyvz commented on the pull request:
https://github.com/apache/spark/pull/9403#issuecomment-157561019
Hi @lordnynex. Why did you think this causes Hive tests to fail? That was
most probably a flaky test.
Regarding publishing a non-aggregated stream, yes that is correct
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157560996
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157560938
**[Test build #46122 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46122/consoleFull)**
for PR 9481 at commit
[`eb411bc`](https://git
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157560211
And yes, SPARK-11672 should be resolved now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157560195
LGTM, indeed a nice improvement :).
---
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/9770#issuecomment-157560144
**[Test build #46130 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46130/consoleFull)**
for PR 9770 at commit
[`9c66274`](https://gith
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157560134
After you push an update, then 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 well. If you
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157560078
Sure, please do, thank you!
---
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 ha
Github user fayeshine commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157559885
Oops, It seems that the API has changed, I'll try to modify as well to save
your effort.
---
If your project is set up for it, you can reply to this email and have yo
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9780#discussion_r45144962
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -492,6 +492,18 @@ private[spark] class TaskSchedulerImpl(
}
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/9780#discussion_r45144733
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -492,6 +492,18 @@ private[spark] class TaskSchedulerImpl(
}
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/9301#issuecomment-157558208
We started to add ubuntu and versions since it wasn't explicit what OS
image it was built upon.
@andrewor14 what are these docker images used for? I'm trying to under
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157557672
**[Test build #46127 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46127/consoleFull)**
for PR 9780 at commit
[`523ba69`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157557402
**[Test build #46128 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46128/consoleFull)**
for PR 9481 at commit
[`eb411bc`](https://gith
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157556347
That's because jersey 2 has a bunch of other dependencies you need aside
from the two jars you're adding. If you find all of them and add them to the
classpath, then it w
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9752#discussion_r45144395
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -422,6 +422,37 @@ private[spark] class MesosCluster
Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157555075
I don't think the javax.ws.rs classes are actually compatible with each
other.
I just tried another experiment. I took my Spark package hacked to remove
the MET
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157554869
**[Test build #46125 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46125/consoleFull)**
for PR 9741 at commit
[`d67a133`](https://gith
Github user jayv commented on a diff in the pull request:
https://github.com/apache/spark/pull/9752#discussion_r45144080
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -422,6 +422,37 @@ private[spark] class MesosClusterSch
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9777#issuecomment-157554794
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9777#issuecomment-157554790
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 n
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157554750
**[Test build #46124 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46124/consoleFull)**
for PR 9779 at commit
[`93939c3`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9777#issuecomment-157554671
**[Test build #46111 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46111/consoleFull)**
for PR 9777 at commit
[`0fd4a91`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157554608
**[Test build #46126 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46126/consoleFull)**
for PR 9656 at commit
[`46ec4a1`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157554609
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-157554666
**[Test build #46129 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46129/consoleFull)**
for PR 9051 at commit
[`1b0a1b7`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157554611
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157554397
If you purge the META-INF stuff, you'll just need to make sure your app has
the newest javax.ws.rs classes available; that may or may not mean adding
exclusions when addi
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9741#discussion_r45143911
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingListenerSuite.scala
---
@@ -320,3 +342,12 @@ class FailureReasonsCollector extends
St
Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157553835
To clarify, does this solution require that I load the jersey 2 jar before
the jersey 1 jar in order to make sure the javax.rs.ws classes are loaded from
jersey 2 in my
Github user fayeshine commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157553929
Dear jkbradley,
Do you mean you plan to fix this patch directly if there's any bug
or problem? I think it's totally OK for me, please fix anything that is n
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-157553605
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-157553588
retest this plseaes
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9301#issuecomment-157553454
@tnachen any comments? Why do we change the mesos version to `-ubuntu`?
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157553559
**[Test build #46126 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46126/consoleFull)**
for PR 9656 at commit
[`46ec4a1`](https://gith
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157553525
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 fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157553256
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157553254
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 tedyu commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157553204
Please take a look at the test and see what should be improved.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user fayeshine commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157553188
The test failed due to the scala style (whitespace problem) and I have
solved it.
Besides, Is the issue11672 solved? Can we add this to the unit test process
since
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157553197
**[Test build #46119 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46119/consoleFull)**
for PR 9481 at commit
[`2714294`](https://git
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9662#discussion_r45143146
--- Diff:
docker-integration-tests/src/test/scala/org/apache/spark/sql/jdbc/PostgresIntegrationSuite.scala
---
@@ -72,11 +78,17 @@ class PostgresIntegratio
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157552644
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
enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9742#issuecomment-157552021
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9742#issuecomment-157552020
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/9742#issuecomment-157551812
**[Test build #46115 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46115/consoleFull)**
for PR 9742 at commit
[`b2bbfee`](https://git
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157551438
The exception you're getting is because you explicitly removed the jersey 1
dependency, right? My suggestion would keep the classes, get rid of the
META-INF stuff. So you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9782#issuecomment-157551087
[Test build #46123 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46123/consoleFull)
for PR 9782 at commit
[`0e40fc8`](https://gith
Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157550160
The exception we're getting here seems like it's a namespace-difference
between Jersey 1 and Jersey 2, and Spark is trying to use Jersey 1's namespace
when the class has
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9692
---
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 tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9752#discussion_r45141605
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -422,6 +422,37 @@ private[spark] class MesosCluster
Github user lordnynex commented on the pull request:
https://github.com/apache/spark/pull/9403#issuecomment-157549725
Despite being closed, I'm confused about why this causes hive unit tests to
fail. Is this unrelated?Also, the publisher in the unit test looks like it's
publishing an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157549665
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9692#issuecomment-157549689
Can you close this PR now that it's merged?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157549586
**[Test build #46116 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46116/consoleFull)**
for PR 9780 at commit
[`2accff3`](https://git
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9692#issuecomment-157549651
By the way @jacek-lewandowski in the future please open against the master
branch, not branch-1.6.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157549666
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157549507
yeah. I can merge this to 1.6 if you add a unit 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 you
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9692#issuecomment-157549266
LGTM merging into master 1.6.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157549041
> For context, my application is pulling in the spark-* artifacts as maven
dependencies
Yeah, that's a different use case, which isn't really covered by my
sugge
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/9782
[HOTFIX][Streaming] Add mockito to fix the compilation error
Added mockito to the test scope to fix the compilation error in branch 1.5
You can merge this pull request into a Git repository by runn
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9758
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9758#issuecomment-157548033
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/9758#issuecomment-157548098
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9758#issuecomment-157547920
OK, merging into master 1.6
---
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 tnachen commented on the pull request:
https://github.com/apache/spark/pull/9752#issuecomment-157547860
Please add [MESOS] and the jira ticket [SPARK-11327] on the title so it
gets picked up the Spark pr tool.
---
If your project is set up for it, you can reply to this em
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9778
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9775#issuecomment-157547601
@tdas @dtolpin can you file a JIRA attached to the title of this PR? See
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9758#issuecomment-157547655
**[Test build #46121 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46121/consoleFull)**
for PR 9758 at commit
[`9125fcf`](https://git
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9781
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9778#issuecomment-157547326
OK
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9781#issuecomment-157546997
Looks OK. I think this is minor enough that it probably doesn't require a
JIRA. Merging into master 1.6.
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7888
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-157546577
Ok, LGTM. I'm merging this into master and 1.6.
We can fix the thing @vanzin pointed out (about not adding the executor to
`executorsPendingToRemove` in the f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6665#issuecomment-157545166
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6665#issuecomment-157545165
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/6665#issuecomment-157544998
**[Test build #46118 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46118/consoleFull)**
for PR 6665 at commit
[`4980835`](https://git
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9670#issuecomment-157542195
@BryanCutler I think `predictOn` should always happen after `trainOn`
because the prediction stream gets registered after `foreachRDD` in `trainOn`
and Spark Streaming wo
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157540330
**[Test build #46122 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46122/consoleFull)**
for PR 9481 at commit
[`eb411bc`](https://gith
Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157539491
I think I have a different issue cropping up that won't be solved by just
not including the META-INF/services/javax.ws.rs files in the assembly.
For context, my
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9758#issuecomment-157539186
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/9758#issuecomment-157539025
**[Test build #46120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46120/consoleFull)**
for PR 9758 at commit
[`5e38c39`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9758#issuecomment-157539187
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user julienledem commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45136673
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/UnsafeRowParquetRecordReader.java
---
@@ -0,0 +1,428 @@
+/*
+
Github user julienledem commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45136577
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/UnsafeRowParquetRecordReader.java
---
@@ -0,0 +1,428 @@
+/*
+
Github user julienledem commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45136501
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/UnsafeRowParquetRecordReader.java
---
@@ -0,0 +1,428 @@
+/*
+
Github user julienledem commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45136485
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/UnsafeRowParquetRecordReader.java
---
@@ -0,0 +1,428 @@
+/*
+
401 - 500 of 942 matches
Mail list logo
