[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread zsxwing
Github user zsxwing commented on the issue: https://github.com/apache/spark/pull/16706 Thanks! Merging to 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 does not have this feature enabled and

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread vanzin
Github user vanzin commented on the issue: https://github.com/apache/spark/pull/16706 LGTM. --- 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

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 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 does not have this feature

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72083/ Test PASSed. ---

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72083 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72083/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72083 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72083/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread zsxwing
Github user zsxwing commented on the issue: https://github.com/apache/spark/pull/16706 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 this feature enabled and wishes so,

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread zsxwing
Github user zsxwing commented on the issue: https://github.com/apache/spark/pull/16706 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 this feature enabled and wishes so,

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72078/ Test FAILed. ---

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 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 does not have this feature

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread zsxwing
Github user zsxwing commented on the issue: https://github.com/apache/spark/pull/16706 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 this feature enabled and wishes so,

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 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 does not have this feature

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-27 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72065/ Test FAILed. ---

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72065 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72065/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 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 does not have this feature

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72047/ Test PASSed. ---

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72047 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72047/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72047 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72047/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72036/ Test PASSed. ---

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 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 does not have this feature

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72036 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72036/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread zsxwing
Github user zsxwing commented on the issue: https://github.com/apache/spark/pull/16706 > However I wonder if a more general change is possible where we say do something like a 'closure cleaning' on the input or output to java serialization to reduce the class information written.

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread zsxwing
Github user zsxwing commented on the issue: https://github.com/apache/spark/pull/16706 cc @vanzin --- 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

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-26 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72036 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72036/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-25 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 Test FAILed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72008/ Test FAILed. ---

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-25 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/16706 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 does not have this feature

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-25 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72008 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72008/testReport)** for PR 16706 at commit

[GitHub] spark issue #16706: [SPARK-19365][Core]Optimize RequestMessage serialization

2017-01-25 Thread SparkQA
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16706 **[Test build #72008 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72008/testReport)** for PR 16706 at commit