Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193608028
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193608023
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193607352
**[Test build #52623 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52623/consoleFull)**
for PR 11571 at commit
[`a64a0a4`](https://g
Github user mwws closed the pull request at:
https://github.com/apache/spark/pull/11571
---
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 mwws commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193562023
OK, thanks for the explanation, I will close this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193560334
But this can only be added to 2.0 (we won't be able to change an existing
release). If users already need to change the constructor in order to use it,
why don't they just
Github user mwws commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-19338
@rxin HiveContext is heavily used by many users now, and many of them still
coupled with old spark version. As this change would be trivial but not
constructive, I think t
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193555075
Thanks for the pull request. So we are actually going to deprecate
HiveContext because it has been one of the most confusing contexts in Spark.
See more in https:/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11571#issuecomment-193553927
**[Test build #52623 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52623/consoleFull)**
for PR 11571 at commit
[`a64a0a4`](https://gi
GitHub user mwws opened a pull request:
https://github.com/apache/spark/pull/11571
[SPARK-13737][SQL][wip]Add getOrCreate method for HiveContext
There is a "getOrCreate" method in SQLContext, which is useful to
recoverable streaming application with SQL operation.
https://spar
10 matches
Mail list logo
