[ https://issues.apache.org/jira/browse/SPARK-33531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mori[A]rty updated SPARK-33531: ------------------------------- Description: Using a new method SparkPlan#executeTakeToIterator to implement CollectLimitExec#executeToIterator to avoid shuffle caused by invoking parent method SparkPlan#executeToIterator. When running a SparkThriftServer and spark.sql.thriftServer.incrementalCollect is enabled, extra shuffle will lead to a significant performance issue for SQLs terminated with LIMIT. was: CollectLimitExec#executeToIterator should be implemented using CollectLimitExec#executeCollect to avoid shuffle caused by invoking parent method SparkPlan#executeToIterator. When running a SparkThriftServer and spark.sql.thriftServer.incrementalCollect is enabled, this will lead to a significant performance issue for SQLs terminated with LIMIT. > [SQL] Avoid shuffle when calling CollectLimitExec#executeToIterator > ------------------------------------------------------------------- > > Key: SPARK-33531 > URL: https://issues.apache.org/jira/browse/SPARK-33531 > Project: Spark > Issue Type: Improvement > Components: SQL > Affects Versions: 2.4.0, 3.0.1 > Reporter: Mori[A]rty > Priority: Major > > Using a new method SparkPlan#executeTakeToIterator to implement > CollectLimitExec#executeToIterator to avoid shuffle caused by invoking parent > method SparkPlan#executeToIterator. > When running a SparkThriftServer and > spark.sql.thriftServer.incrementalCollect is enabled, extra shuffle will lead > to a significant performance issue for SQLs terminated with LIMIT. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org