[jira] [Closed] (SPARK-10199) Avoid using reflections for parquet model save

["Xiangrui Meng (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xiangrui Meng closed SPARK-10199.
---------------------------------
    Resolution: Won't Fix
      Assignee: Vinod KC

Based on the benchmark, we decided not to implement this feature in favor of code readability.

> Avoid using reflections for parquet model save
> ----------------------------------------------
>
>                 Key: SPARK-10199
>                 URL: https://issues.apache.org/jira/browse/SPARK-10199
>             Project: Spark
>          Issue Type: Improvement
>          Components: ML, MLlib
>            Reporter: Feynman Liang
>            Assignee: Vinod KC
>            Priority: Minor
>
> These items are not high priority since the overhead writing to Parquest is much greater than for runtime reflections.
> Multiple model save/load in MLlib use case classes to infer a schema for the data frame saved to Parquet. However, inferring a schema from case classes or tuples uses [runtime reflection|https://github.com/apache/spark/blob/d7b4c095271c36fcc7f9ded267ecf5ec66fac803/sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala#L361] which is unnecessary since the types are already known at the time `save` is called.
> It would be better to just specify the schema for the data frame directly using {{sqlContext.createDataFrame(dataRDD, schema)}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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