You are viewing a plain text version of this content. The canonical link for it is here.

Posted to reviews@spark.apache.org by sujith71955 <gi...@git.apache.org> on 2018/10/10 09:34:49 UTC

[GitHub] spark issue #16677: [SPARK-19355][SQL] Use map output statistics to improve ...

Github user sujith71955 commented on the issue:

    https://github.com/apache/spark/pull/16677
  
    @viirya Are we also looking to optimize CollectLimitExec part? I saw in SparkPlan we have an executeTake() method which basically interpolate the number of partitions and processes the limit query. if driver analyze some statistics about data then i think even this algorithm we can optimize right.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org