You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2019/07/11 02:55:00 UTC
[jira] [Resolved] (SPARK-28306) Once optimizer rule
NormalizeFloatingNumbers is not idempotent
[ https://issues.apache.org/jira/browse/SPARK-28306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-28306.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 25080
[https://github.com/apache/spark/pull/25080]
> Once optimizer rule NormalizeFloatingNumbers is not idempotent
> --------------------------------------------------------------
>
> Key: SPARK-28306
> URL: https://issues.apache.org/jira/browse/SPARK-28306
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Yesheng Ma
> Assignee: Yesheng Ma
> Priority: Major
> Fix For: 3.0.0
>
>
> When the rule NormalizeFloatingNumbers is called multiple times, it will add additional transform operator to an expression, which is not appropriate. To fix it, we have to make it idempotent, i.e. yield the same logical plan regardless of multiple runs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org