Github user smola closed the pull request at:
https://github.com/apache/spark/pull/6177
---
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 smola commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-104030852
@marmbrus Sure. Thanks!
---
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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103995454
Mind closing this? PRs against anything other than master do not auto
close.
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103213593
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103213591
Merged build finished. Test 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 your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103213566
[Test build #33008 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33008/consoleFull)
for PR 6177 at commit
[`c11a428`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103183840
[Test build #33008 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33008/consoleFull)
for PR 6177 at commit
[`c11a428`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103183452
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103183515
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-103182880
ok to test
---
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
en
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-102298343
Jenkins, ok to test.
---
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 fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6177#issuecomment-102296114
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 pr
GitHub user smola opened a pull request:
https://github.com/apache/spark/pull/6177
[SPARK-7566][SQL] Add type to HiveContext.analyzer
This makes HiveContext.analyzer overrideable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sm
Github user smola commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-102295560
@rxin Ok. Here's the PR for branch-1.3:
https://github.com/apache/spark/pull/6177
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-102108928
This fails to cherry-pick. Can you submit a patch against branch-1.3? I can
merge it that way.
---
If your project is set up for it, you can reply to this email and have
Github user smola commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101999128
@rxin Any chance to merge this to branch-1.3 too?
---
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 p
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6086
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101536352
Thanks. I've merged this in master & branch-1.4.
---
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 pro
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101534879
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101534875
Merged build finished. Test 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 your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101534843
[Test build #32578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32578/consoleFull)
for PR 6086 at commit
[`8ece136`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101512331
[Test build #32578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32578/consoleFull)
for PR 6086 at commit
[`8ece136`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101512192
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/6086#issuecomment-101512183
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 h
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101512025
Jenkins, retest 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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101486767
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101486758
**[Test build #32551 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32551/consoleFull)**
for PR 6086 at commit
[`8ece136`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101486766
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101464634
[Test build #32551 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32551/consoleFull)
for PR 6086 at commit
[`8ece136`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101464547
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101464561
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101464090
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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6086#issuecomment-101339445
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 pr
GitHub user smola opened a pull request:
https://github.com/apache/spark/pull/6086
[SPARK-7566][SQL] Add type to HiveContext.analyzer
This makes HiveContext.analyzer overrideable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sm
34 matches
Mail list logo
