Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17489
OK, then "-1100" doesn't work right now, though it used to. ZZ is supposed
to support "-1100" according to the Java docs, but then again, that also
suggests some things don't work which do actually work because we're using
FastDateFormat. ZZ actually means, to FastDateFormat, what XXX means to the
Java implementation? but both interpret XXX the same way?
It does seem simpler to standardize on XXX because it's clearer all around,
if they both behave the same way and behave how ZZ already behaves. In that
case, we do want to update the doc and implementation to use XXX, I think.
The problem is that "-1100" should have worked according to docs but
didn't? I think that it's OK for it to continue to not work then.
More importantly, this is supposed to be the ISO 8601 default format right?
and XXX means that, not ZZ.
It's a complex situation but I think this is good change for 2.2. Of
course, this only affects the default. One can override with any specific
format.
---
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]
