You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2019/03/04 02:48:00 UTC
[jira] [Resolved] (SPARK-27001) Refactor "serializerFor" method
between ScalaReflection and JavaTypeInference
[ https://issues.apache.org/jira/browse/SPARK-27001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-27001.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23908
[https://github.com/apache/spark/pull/23908]
> Refactor "serializerFor" method between ScalaReflection and JavaTypeInference
> -----------------------------------------------------------------------------
>
> Key: SPARK-27001
> URL: https://issues.apache.org/jira/browse/SPARK-27001
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Minor
> Fix For: 3.0.0
>
>
> While we address SPARK-22000 we refactored "deserializer" method between ScalaReflection and JavaTypeInference since lots of things were duplicated, and even code had been diverged to let Java side missing upcast.
> Once we take a step on refactoring, I would propose refactoring "serializerFor" since similar duplications are observed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org