Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-45053194
Hey - I still haven't heard back from the Mesos folks, by I'm fairly sure
they are wire-compatible across client library versions. If not, this patch can
be trivially
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/920
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44719879
Sean - do you mind fixing the style violation (100 char wide lines)? Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44744577
Oops, yes, coming up 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 project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44744579
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/920#issuecomment-44744576
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/920#issuecomment-44745345
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15319/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44745344
Merged build finished. All automated tests passed.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44755003
Hey Sean - do you know if this will break Spark for Mesos 15/16/17? When
did the introduce the newer API? We should definitely update this... I'm a bit
concerned about
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44755392
Yes looks like it was introduced in 0.17.0:
https://github.com/apache/mesos/commit/b609c851493c81c6ba8dfe51cf102400c05c2d0c
I see, I thought the intent was to
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44755561
So I've actually been assuming that users running older versions of Mesos
just change `mesos.version` in the build and package Spark, so in my head I've
sort of coupled
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44649192
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/920#issuecomment-44649200
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 srowen opened a pull request:
https://github.com/apache/spark/pull/920
SPARK-1806 (addendum) Use non-deprecated methods in Mesos 0.18
The update to Mesos 0.18 caused some deprecation warnings in the build. The
change to the non-deprecated version is straightforward as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44649359
Merged build finished.
---
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/920#issuecomment-44649361
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15305/
---
If your project is set up for it, you can
16 matches
Mail list logo
