[
https://issues.apache.org/jira/browse/SPARK-16216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383772#comment-15383772
]
Sean Owen commented on SPARK-16216:
-----------------------------------
They output without a timezone? my main concern is that this is ambiguous
output, unless somehow "GMT" or "UTC" is implied for JSON always. That is,
"1970-01-01 11:46:40.0" is not a time. "1970-01-01 11:46:40.0 GMT" is. I can
appreciate the argument that it shouldn't change in JSON even if it's not
right, but, would we actually port the problem to CSV?
> CSV data source does not write date and timestamp correctly
> -----------------------------------------------------------
>
> Key: SPARK-16216
> URL: https://issues.apache.org/jira/browse/SPARK-16216
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Hyukjin Kwon
> Priority: Minor
>
> Currently, CSV data source write {{DateType}} and {{TimestampType}} as below:
> {code}
> +----------------+
> | date|
> +----------------+
> |1440637200000000|
> |1414459800000000|
> |1454040000000000|
> +----------------+
> {code}
> It would be nicer if it write dates and timestamps as a formatted string just
> like JSON data sources.
> Also, CSV data source currently supports {{dateFormat}} option to read dates
> and timestamps in a custom format. It might be better if this option can be
> applied in writing as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
