[ https://issues.apache.org/jira/browse/SPARK-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen updated SPARK-19091: ------------------------------- Comment: was deleted (was: Upon closer inspection, I think the right approach here might be to simply not construct a LogicalRDD when going from a ParallelCollectionRDD to a Dataset. Instead, we should probably just jump right to a LocalRelation similar to what we do in createDataFrame()'s Seq-taking overload.) > createDataset(sc.parallelize(x: Seq)) should be equivalent to > createDataset(x: Seq) > ----------------------------------------------------------------------------------- > > Key: SPARK-19091 > URL: https://issues.apache.org/jira/browse/SPARK-19091 > Project: Spark > Issue Type: Improvement > Components: SQL > Reporter: Josh Rosen > > It turns out that spark.createDataset(sc.parallelize(x: Seq)) and > spark.createaDataSet(x: Seq) produce different plans, where the former is > much less efficient due to a lack of accurate size estimation. We should > modify SparkSession to special-case the situation where createDataset is > called on a ParallelCollectionRDD in order to remove this source of > performance variation between the two plans. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org