Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17489
I tested "-1100" cases
[before](https://issues.apache.org/jira/browse/SPARK-17545?focusedCommentId=15509110&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15509110)
with `ZZ`.
I _guess_ this was rather a bug in commons-lang but fixed after we upgrade
commons-lang [SPARK-17985](https://issues.apache.org/jira/browse/SPARK-17985).
I just downloaded Spark 2.0.0 and test the codes below:
```scala
scala>
org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-1100")
res2: java.util.Date = Tue Mar 21 20:00:00 KST 2017
```
Spark 2.1.0:
```scala
scala>
org.apache.commons.lang3.time.FastDateFormat.getInstance("yyyy-MM-dd'T'HH:mm:ss.SSSZZ").parse("2017-03-21T00:00:00.000-1100")
java.text.ParseException: Unparseable date: 2017-03-21T00:00:00.000-1100
at
org.apache.commons.lang3.time.FastDateParser.parse(FastDateParser.java:371)
at
org.apache.commons.lang3.time.FastDateFormat.parse(FastDateFormat.java:545)
... 48 elided
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
