Github user darose commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42602116
I tried building an running this code, but it failed with:
14/05/08 20:09:11 ERROR Remoting:
org.apache.spark.deploy.ApplicationDescription; local class incompatibl
Github user darose commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42672273
Thanks for the suggestions. I don't think this is a deployment issue
though. I don't have any spark/shark remnants installed from packages on the
client machine. (I don'
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42644509
`json4s` is a direct dependency of Spark core. It's not related to the
changes here. It sounds like something is running but being pointed to an
artifact that does not cont
Github user darose commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42635850
I tried downloading the latest from the master branch of both spark and
shark, and built and ran them (in the hopes of getting past that "class
incompatible" issue) but no
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42673811
Although there's now a 'fix' in, it is only going to do automatically what
you are doing by hand.
My hunch is that perhaps the script, or env variable, already contains
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42616622
So this means that the Java-serialized format of a Spark class has changed
(or at least, it may have; the serialVersionUID changed) between the versions
of two Spark compon
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/629
---
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 enabl
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42213788
All set here. I think it does fix the issue and make future, similar
changes easier to apply in maven, so I'm for it.
---
If your project is set up for it, you can reply t
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42213357
@srowen looks good to me! Is there anything else you plan to add to this or
is it ready to go?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42175676
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42175679
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14662/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42175500
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42175502
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14661/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42173644
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42173652
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12272908
--- Diff: docs/building-with-maven.md ---
@@ -42,22 +55,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and
other Hadoop versions wit
# Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42173056
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42173066
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 commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42171989
OK, but leave default `hadoop.version=1.0.4`? OK. I can make a `hadoop-2.4`
profile if you're not concerned about having the extra stanza to maintain.
---
If your project
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12272356
--- Diff: docs/building-with-maven.md ---
@@ -42,22 +54,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and
other Hadoop versions wit
# Apache
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42158974
Thanks @srowen! I tested this and it seems to work well (tests below).
Comments are inline. My main thoughts were:
1. It might be nicer to ask people to always
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12266975
--- Diff: docs/building-with-maven.md ---
@@ -42,22 +54,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and
other Hadoop versions wit
# Apac
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12266954
--- Diff: docs/building-with-maven.md ---
@@ -42,22 +54,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and
other Hadoop versions wit
# Apac
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12266958
--- Diff: docs/building-with-maven.md ---
@@ -42,22 +54,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and
other Hadoop versions wit
# Apac
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12266937
--- Diff: docs/building-with-maven.md ---
@@ -42,22 +54,40 @@ For Apache Hadoop versions 1.x, Cloudera CDH MRv1, and
other Hadoop versions wit
# Apac
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42132419
Looks good to me.
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12261171
--- Diff: core/pom.xml ---
@@ -38,12 +38,6 @@
net.java.dev.jets3t
jets3t
-
-
- commons-logging
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/629#discussion_r12261160
--- Diff: core/pom.xml ---
@@ -38,12 +38,6 @@
net.java.dev.jets3t
jets3t
-
-
- commons-logging
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42129265
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42129266
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14641/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42128538
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/629#issuecomment-42128534
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 ha
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/629
SPARK-1556. jets3t dep doesn't update properly with newer Hadoop versions
See related discussion at https://github.com/apache/spark/pull/468
This PR may still overstep what you have in mind, b
33 matches
Mail list logo
