[
https://issues.apache.org/jira/browse/SPARK-6459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553330#comment-16553330
]
Michael Armbrust commented on SPARK-6459:
-----------------------------------------
[~tenstriker] this will never happen from a SQL query. This only happens when
you take already resolved attributes from different parts of a DataFrame and
manually construct an equality that can't be differentiated.
> Warn when Column API is constructing trivially true equality
> ------------------------------------------------------------
>
> Key: SPARK-6459
> URL: https://issues.apache.org/jira/browse/SPARK-6459
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.3.0
> Reporter: Michael Armbrust
> Assignee: Michael Armbrust
> Priority: Critical
> Fix For: 1.3.1, 1.4.0
>
>
> Right now its pretty confusing when a user constructs and equality predicate
> that is going to be use in a self join, where the optimizer cannot
> distinguish between the attributes in question (e.g., [SPARK-6231]). Since
> there is really no good reason to do this, lets print a warning.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
