Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37405632
Yes the build failed for me with the error I put above.
Note that this pr would need to have the maven build updated too.
---
If your project is set up for it,
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37394958
@pwendell Yes that's the thing. While the repo was down I could still build
the whole project from an empty repo. For artifacts like paho, where it's found
not in the 3 rep
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37377699
@rxin Sorry for comment bomb but actually before merging this let's check
if it bumps any recursive dependencies. I can take a look on that.
---
If your project is set u
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37377565
Btw the reason I'm +1 on this is that we should try to upgrade these things
going into 1.0 so we don't end up with super old versions of everything as the
1.X wears on. I
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37377469
@srowen yep the repo is there for convenience of CDH users mostly for
historical reasons (for a while CDH was the only way you could get the Hadoop2
code). What I don't u
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37377281
That sounds good. @pwendell should make the call here ...
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37332343
What exactly do you want tried? I built it for hadoop2 with sbt and ran a
couple of the examples on yarn SparkPi and SparkHdfsLR. Those worked fine and
the UI still wo
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37249125
Ok I think the cloduera repo is up. @tgravescs it would be great if you can
try this.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37232830
Yeah the Cloudera repo is down today. I know the ops guys are figuring out
why but don't see an ETA. While the repo ought to be, ahem, pretty reliable, it
looks like it use
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37232635
@tgravescs the cloudera repo is down (I spoke with them) and they are
trying to get it back up.
---
If your project is set up for it, you can reply to this email and ha
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37230554
Yea unfortunately that's been the case for the past few days We should
probably have another external repo to host artifacts only on cloudera repo to
have some redundanc
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37230471
I generally use mvn to build. Right now I seem to be having issues
building at all due to what appears like the cloudera repository being down.
Error resolving
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37213133
The main reason is that we are investigating upgrading some of the major
dependencies prior to 1.0, after which we won't be able to upgrade for a while.
Some users have reque
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37212561
Actually I was waiting for the pull request builder to come back before
asking you to verify it. @tgravescs do you mind verifying this works for you? I
haven't updated the Ma
14 matches
Mail list logo
