You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by uncleGen <gi...@git.apache.org> on 2016/12/01 05:15:17 UTC
[GitHub] spark pull request #16096: [SPARK-18617][BACKPORT] backport to branch-2.0
GitHub user uncleGen opened a pull request:
https://github.com/apache/spark/pull/16096
[SPARK-18617][BACKPORT] backport to branch-2.0
## What changes were proposed in this pull request?
backport #16052 to branch-2.0 with incremental update in #16091
## How was this patch tested?
new unit test
cc @zsxwing @rxin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uncleGen/spark branch-2.0-SPARK-18617
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16096.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #16096
----
commit 76e01432398295f8c48606dbba4847eede3815a2
Author: uncleGen <hu...@gmail.com>
Date: 2016-12-01T05:07:59Z
backport to branch-2.0
----
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] Follow up PR to Close "kryo auto...
Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16096
**[Test build #69455 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69455/consoleFull)** for PR 16096 at commit [`76e0143`](https://github.com/apache/spark/commit/76e01432398295f8c48606dbba4847eede3815a2).
* This patch passes all tests.
* This patch merges cleanly.
* This patch adds no public classes.
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] Follow up PR to Close "kryo auto...
Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16096
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69455/
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] backport to branch-2.0
Posted by rxin <gi...@git.apache.org>.
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16096
Can you use a meaningful title & description instead of saying backport? This is important because it becomes part of the commit history.
You can put the backport message in the body. 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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] Follow up PR to Close "kryo auto...
Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16096
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request #16096: [SPARK-18617][BACKPORT] Follow up PR to Close "kr...
Posted by uncleGen <gi...@git.apache.org>.
Github user uncleGen closed the pull request at:
https://github.com/apache/spark/pull/16096
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] backport to branch-2.0
Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16096
**[Test build #69455 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69455/consoleFull)** for PR 16096 at commit [`76e0143`](https://github.com/apache/spark/commit/76e01432398295f8c48606dbba4847eede3815a2).
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] Follow up PR to Close "kryo auto...
Posted by rxin <gi...@git.apache.org>.
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16096
Merging in. Can you close the pull request? It won't auto close because it's not merged in 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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org