Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18853
Currently, the type casting has a few issues when types are different. So
far, we do not have any good option to resolve all the issues. Thus, we are
hesitant to introduce any behavior change
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18853
If we change this behaviour, I think we better modify code in
`findCommonTypeForBinaryComparison` of `TypeCoercion` instead of your pr:
Github user wangyum commented on the issue:
https://github.com/apache/spark/pull/18853
Thanks @maropu, There are some problems:
```:sql
spark-sql> select "20" > "100";
true
spark-sql>
```
So [`tmap.tkey <
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18853
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80339/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18853
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/18853
**[Test build #80339 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80339/testReport)**
for PR 18853 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18853
**[Test build #80339 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80339/testReport)**
for PR 18853 at commit
Github user wangyum commented on the issue:
https://github.com/apache/spark/pull/18853
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 user wangyum commented on the issue:
https://github.com/apache/spark/pull/18853
Casting the `int` values into `string` can works, but filter a int column
with string type feels terrible.
My opinion is cast filter value to column type.
---
If your project is set up for
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18853
How about casting the `int` values into `string` ones in that case you
described in the description, and then comparing them by a lexicographical
order?
---
If your project is set up for it, you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18853
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/18853
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80286/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18853
**[Test build #80286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80286/testReport)**
for PR 18853 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18853
**[Test build #80286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80286/testReport)**
for PR 18853 at commit
14 matches
Mail list logo
