[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

2017-04-12 Thread dbtsai
Github user dbtsai commented on the issue: https://github.com/apache/spark/pull/17618 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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

2017-04-12 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17618 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 #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

2017-04-12 Thread gatorsmile
Github user gatorsmile commented on the issue: https://github.com/apache/spark/pull/17618 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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

2017-04-12 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17618 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 #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

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

[GitHub] spark issue #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

2017-04-12 Thread AmplabJenkins
Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/17618 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 #17618: [SPARK-20291][SQL][BACKPORT] NaNvl(FloatType, NullType) ...

2017-04-12 Thread dbtsai
Github user dbtsai commented on the issue: https://github.com/apache/spark/pull/17618 @viirya Added. 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