You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:15:25 UTC
[jira] [Resolved] (SPARK-20095) A code bug in
CodegenContext.withSubExprEliminationExprs
[ https://issues.apache.org/jira/browse/SPARK-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-20095.
----------------------------------
Resolution: Incomplete
> A code bug in CodegenContext.withSubExprEliminationExprs
> --------------------------------------------------------
>
> Key: SPARK-20095
> URL: https://issues.apache.org/jira/browse/SPARK-20095
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.1.0
> Reporter: song fengfei
> Priority: Major
> Labels: bulk-closed
>
> In the function:CodegenContext.withSubExprEliminationExprs...{
> val oldsubExprEliminationExprs = subExprEliminationExprs
> subExprEliminationExprs.clear
> ...
> // Restore previous subExprEliminationExprs
> subExprEliminationExprs.clear
> oldsubExprEliminationExprs.foreach(subExprEliminationExprs += _)
> }
> it seems that the oldsubExprEliminationExprs and subExprEliminationExprs are the same instance,after the second subExprEliminationExprs.clear ,the oldsubExprEliminationExprs is also cleared,so,the previous subExprEliminationExprs in CodegenContext will not be Restored.
> Is it a bug?
--
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