Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53883407
can you separate these 2 changes. The test change would need to go into
master and branch-1.1. The other is just for branch-1.1
---
If your project is set up for it,
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53883744
sure, but SPARK-3177 can't run without pom.xml changes.
On Fri, Aug 29, 2014 at 7:32 AM, Tom Graves notificati...@github.com
wrote:
can
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53884482
Just to clear, so you mean I need to
1) close the current PR
2) open two PRs, one for pom.xml changes and another one for test changes ?
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53884847
Yes please close this one. Open just one new one with SPARK-3177 against
master branch and I'll pull back into branch-1.1 also. Leave the pom.xml
change out since
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53887249
sure, will do
On Fri, Aug 29, 2014 at 7:43 AM, Tom Graves notificati...@github.com
wrote:
Yes please close this one. Open just one new
Github user chesterxgchen closed the pull request at:
https://github.com/apache/spark/pull/2111
---
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
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53915017
Close based on tgravescs sugegstions
---
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 chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53916084
new PR is created at
https://github.com/apache/spark/pull/2204
On Fri, Aug 29, 2014 at 7:58 AM, Chester Chen ches...@alpinenow.com wrote:
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53436623
Which versions of hadoop are you using when you say yarn-alpha vs yarn?
hadoop 0.23 doesn't even contain DEFAULT_MAPREDUCE_APPLICATION_CLASSPATH so I
assume you are
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53455378
I am using 2.0.5-alpha. This is our internal setup we use.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53456331
To be clarify, this is the version we use internally to support our customer
---
If your project is set up for it, you can reply to this email and have your
reply
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53462912
We should check to see if i changed in any of the other minor versions
before hadoop2.2. Otherwise it will work for you but not others.
---
If your project is set up
Github user chesterxgchen commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53474088
I just checked against 2.0.6-alpha, the test passed as well.
Notice that 2.0.6-alpha is released in Aug. 2013, after 0.23.9 in July,
2013
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53475232
thanks for looking at 2.0.6. The 0.23 branch and the 2.x branch are not
comparable as far as the timelines. I'll take a look at a few others.
---
If your project is
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53478704
Ok it looks like it was an array up until the 2.2 release so this is safe.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53263503
Jenkins, test 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53264010
QA tests have started for PR 2111. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19138/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53274969
QA results for PR 2111:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
GitHub user chesterxgchen opened a pull request:
https://github.com/apache/spark/pull/2111
SPARK-3177 : Yarn-alpha ClientBaseSuite Unit test failed
This second try to fix the Yarn-Alpha unit test failure due to Yarn API
changes.
I have to include SPARK-3175 (pom.xml)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2111#issuecomment-53218717
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
20 matches
Mail list logo
