You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Damian Momot (JIRA)" <ji...@apache.org> on 2016/11/17 12:37:58 UTC
[jira] [Comment Edited] (SPARK-18491) Spark uses mutable classes
for date/time types mapping
[ https://issues.apache.org/jira/browse/SPARK-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15673608#comment-15673608 ]
Damian Momot edited comment on SPARK-18491 at 11/17/16 12:37 PM:
-----------------------------------------------------------------
Until Java 8 is available spark could do what all other JVM data mapping libraries are doing - allow to use Joda Time classes which solved mutability problem long ago and were defacto standard java date/time types before JDK8 was released.
was (Author: daimon):
Until Java 8 is available spark could do what all other JVM data mapping libraries are doing - allow to use Joda Time classes which solved mutability problem long ago and were defacto standard java date/time types until JDK8 was released.
> Spark uses mutable classes for date/time types mapping
> ------------------------------------------------------
>
> Key: SPARK-18491
> URL: https://issues.apache.org/jira/browse/SPARK-18491
> Project: Spark
> Issue Type: Improvement
> Reporter: Damian Momot
> Priority: Minor
>
> TimestampType is mapped to java.sql.Timestamp
> DateType is mapped to java.sql.Date
> Those both java types are mutable and thus their usage is highly discourage, especially in distributed computing which uses lazy, functional approach
> Mapping to immutable joda times should be enough for now (until scala 2.12 + jdk8 java.time is available for spark)
--
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