Github user ianoc commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-49950192
Excellent 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 feature
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-49950149
Thanks! I've merged this into master.
---
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 do
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1377
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-49949863
QA results for PR 1377:- This patch PASSES unit tests.- This patch
merges cleanly- This patch adds the following public classes
(experimental):if an unregistered class is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-49941046
QA tests have started for PR 1377. This patch merges cleanly. View
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/17062/consoleFull
---
If
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-49940651
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 this featu
Github user ianoc commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-49701073
@pwendell Sounds good to me, updated as per your suggestion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1377#discussion_r15211673
--- Diff: docs/configuration.md ---
@@ -382,6 +382,16 @@ Apart from these, the following properties are also
available, and may be useful
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-48934357
@pwendell, any thoughts on the additional option for kryo?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-48860618
QA results for PR 1377:- This patch PASSES unit tests.- This patch
merges cleanly- This patch adds no public classesFor more
information see test
ouptut:https://amplab.c
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-48857093
QA tests have started for PR 1377. This patch merges cleanly. View
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16610/consoleFull
---
If
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-48857036
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 this featu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1377#issuecomment-48790373
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 pro
GitHub user ianoc opened a pull request:
https://github.com/apache/spark/pull/1377
[SQL][CORE] SPARK-2102
Adds in an option into the kryo serializer to enable requiring registration
Adds a resource pool in the SparkSqlSerializer code paths to speed up
serialization of gener
14 matches
Mail list logo
