Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
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 user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68940/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68940 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68940/consoleFull)**
for PR 15956 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68940 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68940/consoleFull)**
for PR 15956 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
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 user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68938/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68938 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68938/consoleFull)**
for PR 15956 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68938 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68938/consoleFull)**
for PR 15956 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68932/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
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 user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68932 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68932/consoleFull)**
for PR 15956 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68932 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68932/consoleFull)**
for PR 15956 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15956
> Spark SQL currently has a restriction that we just don't allow map types
to be used in equality comparison at all, but I don't want to structure code in
a way that would make it harder to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68920/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15956
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 user rxin commented on the issue:
https://github.com/apache/spark/pull/15956
So technically I think map type should be able to be used in equality
comparison, but not orderable, so I'm not sure if this is correct.
Spark SQL currently has a restriction that we just
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68920 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68920/consoleFull)**
for PR 15956 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15956
cc @yhuai @hvanhovell @gatorsmile
---
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
18 matches
Mail list logo
