[ https://issues.apache.org/jira/browse/SPARK-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148776#comment-15148776 ]
Sean Owen commented on SPARK-2421: ---------------------------------- Pretty much the same reason in all cases: no activity in 16 months, a nice-to-have (i.e. not a known bug), nobody asking for it or putting any work into or reason to expect activity. It's more fruitful to reflect reality -- and then if desired ask, why is nobody (like yourself) working on it if you are interested? Or: reopen it but please, only if there is a good-faith reason to expect someone will work on it imminently. Remember, things can be reopened later. Worst case, new issues can be opened. We can also make a different resolution like "Later" if people find that softer. > Spark should treat writable as serializable for keys > ---------------------------------------------------- > > Key: SPARK-2421 > URL: https://issues.apache.org/jira/browse/SPARK-2421 > Project: Spark > Issue Type: Improvement > Components: Input/Output, Java API > Affects Versions: 1.0.0 > Reporter: Xuefu Zhang > > It seems that Spark requires the key be serializable (class implement > Serializable interface). In Hadoop world, Writable interface is used for the > same purpose. A lot of existing classes, while writable, are not considered > by Spark as Serializable. It would be nice if Spark can treate Writable as > serializable and automatically serialize and de-serialize these classes using > writable interface. > This is identified in HIVE-7279, but its benefits are seen global. -- 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