Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-68376619
Branch-1.1 backport is here: #3768
---
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
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/3763
[SPARK-4920][UI]:current spark version in UI is not striking.
It is not convenient to see the Spark version. We can keep the same style
with Spark website.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67852386
[Test build #24705 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24705/consoleFull)
for PR 3763 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67863235
[Test build #24705 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24705/consoleFull)
for PR 3763 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67863240
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67878388
+1. I also thought the bottom greyed out text is too obscure. @JoshRosen
any thoughts?
---
If your project is set up for it, you can reply to this email and have
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67892439
@srowen [commented on the
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67892496
By the way, if we merge this it should also go into `branch-1.1`.
---
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/3763#issuecomment-67892847
Meh, on looking at it again, I like the new version that's consistent with
the website. It's only devs that will look at long SNAPSHOT names. It's a clean
change too.
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67897075
Alright, sounds good then I'm going to merge this into master 1.2 and 1.1
thanks guys
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3763
---
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67907393
@andrewor14 would you mind merging this into `branch-1.1` also?
@JoshRosen pointed out it should go there too
---
If your project is set up for it, you can reply to
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67907587
@ash211 I think that Andrew [tried
this](https://github.com/apache/spark/pull/3763#issuecomment-67897075), but
there was a merge conflict:
For 1.1, it
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/3763#issuecomment-67923578
Oh whoops my apologies for the noise
---
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
14 matches
Mail list logo
