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

Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2014/05/29 04:56:02 UTC

[jira] [Created] (SPARK-1958) Calling .collect() on a SchemaRDD should call executeCollect() on the underlying query plan.

Michael Armbrust created SPARK-1958:
---------------------------------------

             Summary: Calling .collect() on a SchemaRDD should call executeCollect() on the underlying query plan.
                 Key: SPARK-1958
                 URL: https://issues.apache.org/jira/browse/SPARK-1958
             Project: Spark
          Issue Type: Bug
          Components: SQL
    Affects Versions: 1.0.0
            Reporter: Michael Armbrust
             Fix For: 1.1.0


In some cases (like LIMIT) executeCollect() makes optimizations that execute().collect() will not.



--
This message was sent by Atlassian JIRA
(v6.2#6252)