[ https://issues.apache.org/jira/browse/SPARK-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015158#comment-14015158 ]
Cheng Lian commented on SPARK-1958: ----------------------------------- PR: https://github.com/apache/spark/pull/939 > 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 > Assignee: Cheng Lian > 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)