[
https://issues.apache.org/jira/browse/SPARK-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539503#comment-14539503
]
Reynold Xin commented on SPARK-7562:
------------------------------------
This is related to https://issues.apache.org/jira/browse/SPARK-6444
and also there is one past attempt at this problem:
https://github.com/apache/spark/pull/4685
#4685 pull request only marks expressions as unresolved, but doesn't report any
error to users (e.g. we should explain why "1 + date" is invalid).
cc [~kai-zeng]
> Improve error reporting for expression data type mismatch
> ---------------------------------------------------------
>
> Key: SPARK-7562
> URL: https://issues.apache.org/jira/browse/SPARK-7562
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Reporter: Reynold Xin
>
> There is currently no error reporting for expression data types in analysis
> (we rely on "resolved" for that, which doesn't provide great error messages
> for types). It would be great to have that in checkAnalysis.
> Ideally, it should be the responsibility of each Expression itself to specify
> the types it requires, and report errors that way. We would need to define a
> simple interface for that so each Expression can implement. The default
> implementation can just use the information provided by
> ExpectsInputTypes.expectedChildTypes.
> cc [~marmbrus] what we discussed offline today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
