Uh oh!
There was an error while loading. Please reload this page.
[SPARK-17108][SQL]: Fix BIGINT and INT comparison failure in spark sql - #15448
Closed
weiqingy wants to merge 3 commits into
Closed
[SPARK-17108][SQL]: Fix BIGINT and INT comparison failure in spark sql#15448weiqingy wants to merge 3 commits into
weiqingy wants to merge 3 commits into
Conversation
hvanhovell
commented
Oct 12, 2016
Contributor
Could you try to fix this by adding implicit casting to the |
Contributor
Also add a unit test please. |
SparkQA
commented
Oct 12, 2016
Test build #3330 has finished for PR 15448 at commit
|
weiqingy
commented
Oct 12, 2016
ContributorAuthor
Hi, @hvanhovell Thanks for the quick feedback. Yes, I will update the PR. |
weiqingy
commented
Oct 15, 2016
ContributorAuthor
Hi, @hvanhovell I have updated the PR, could you help review it again? |
weiqingy
commented
Oct 20, 2016
ContributorAuthor
Hi, @hvanhovell Could you review this PR again? Thanks. |
1 similar comment
weiqingy
commented
Oct 26, 2016
ContributorAuthor
Hi, @hvanhovell Could you review this PR again? Thanks. |
hvanhovell
commented
Nov 7, 2016
Contributor
LGTM. Merging to master/2.1. Thanks! My apologies for the long wait! |
asfgit pushed a commit
that referenced
this pull request
Nov 7, 2016
## What changes were proposed in this pull request?
Add a function to check if two integers are compatible when invoking `acceptsType()` in `DataType`.
## How was this patch tested?
Manually.
E.g.
```
spark.sql("create table t3(a map<bigint, array<string>>)")
spark.sql("select * from t3 where a[1] is not null")
```
Before:
```
cannot resolve 't.`a`[1]' due to data type mismatch: argument 2 requires bigint type, however, '1' is of int type.; line 1 pos 22
org.apache.spark.sql.AnalysisException: cannot resolve 't.`a`[1]' due to data type mismatch: argument 2 requires bigint type, however, '1' is of int type.; line 1 pos 22
at org.apache.spark.sql.catalyst.analysis.package$AnalysisErrorAt.failAnalysis(package.scala:42)
at org.apache.spark.sql.catalyst.analysis.CheckAnalysis$$anonfun$checkAnalysis$1$$anonfun$apply$2.applyOrElse(CheckAnalysis.scala:82)
at org.apache.spark.sql.catalyst.analysis.CheckAnalysis$$anonfun$checkAnalysis$1$$anonfun$apply$2.applyOrElse(CheckAnalysis.scala:74)
at org.apache.spark.sql.catalyst.trees.TreeNode$$anonfun$transformUp$1.apply(TreeNode.scala:307)
```
After:
Run the sql queries above. No errors.
Author: Weiqing Yang <yangweiqing001@gmail.com>
Closes#15448 from weiqingy/SPARK_17108.
(cherry picked from commit 0d95662)
Signed-off-by: Herman van Hovell <hvanhovell@databricks.com>weiqingy
commented
Nov 7, 2016
ContributorAuthor
@hvanhovell Thanks for the review! |
zzcclp added a commit
to zzcclp/spark
that referenced
this pull request
Nov 15, 2016
uzadude pushed a commit
to uzadude/spark
that referenced
this pull request
Jan 27, 2017
## What changes were proposed in this pull request?
Add a function to check if two integers are compatible when invoking `acceptsType()` in `DataType`.
## How was this patch tested?
Manually.
E.g.
```
spark.sql("create table t3(a map<bigint, array<string>>)")
spark.sql("select * from t3 where a[1] is not null")
```
Before:
```
cannot resolve 't.`a`[1]' due to data type mismatch: argument 2 requires bigint type, however, '1' is of int type.; line 1 pos 22
org.apache.spark.sql.AnalysisException: cannot resolve 't.`a`[1]' due to data type mismatch: argument 2 requires bigint type, however, '1' is of int type.; line 1 pos 22
at org.apache.spark.sql.catalyst.analysis.package$AnalysisErrorAt.failAnalysis(package.scala:42)
at org.apache.spark.sql.catalyst.analysis.CheckAnalysis$$anonfun$checkAnalysis$1$$anonfun$apply$2.applyOrElse(CheckAnalysis.scala:82)
at org.apache.spark.sql.catalyst.analysis.CheckAnalysis$$anonfun$checkAnalysis$1$$anonfun$apply$2.applyOrElse(CheckAnalysis.scala:74)
at org.apache.spark.sql.catalyst.trees.TreeNode$$anonfun$transformUp$1.apply(TreeNode.scala:307)
```
After:
Run the sql queries above. No errors.
Author: Weiqing Yang <yangweiqing001@gmail.com>
Closesapache#15448 from weiqingy/SPARK_17108.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Add a function to check if two integers are compatible when invoking
acceptsType()inDataType.How was this patch tested?
Manually.
E.g.
Before:
After:
Run the sql queries above. No errors.