You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hannu Kröger (JIRA)" <ji...@apache.org> on 2018/10/02 13:02:00 UTC
[jira] [Commented] (SPARK-25497) limit operation within whole stage
codegen should not consume all the inputs
[ https://issues.apache.org/jira/browse/SPARK-25497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635443#comment-16635443 ]
Hannu Kröger commented on SPARK-25497:
--------------------------------------
Note: This also affects 2.3.0.
> limit operation within whole stage codegen should not consume all the inputs
> ----------------------------------------------------------------------------
>
> Key: SPARK-25497
> URL: https://issues.apache.org/jira/browse/SPARK-25497
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.4.0
> Reporter: Wenchen Fan
> Priority: Major
>
> This issue was discovered during https://github.com/apache/spark/pull/21738 .
> It turns out that limit is not whole-stage-codegened correctly and always consume all the inputs
--
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