You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2017/12/27 19:12:03 UTC

[jira] [Updated] (PIG-3864) ToDate(userstring, format, timezone) computes DateTime with strange handling of Daylight Saving Time with location based timezones

     [ https://issues.apache.org/jira/browse/PIG-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohini Palaniswamy updated PIG-3864:
------------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

+1. Committed to trunk.

> ToDate(userstring, format, timezone) computes DateTime with strange handling of Daylight Saving Time with location based timezones
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-3864
>                 URL: https://issues.apache.org/jira/browse/PIG-3864
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.12.0, 0.11.1
>            Reporter: Frederic Schmaljohann
>            Assignee: Daniel Dai
>             Fix For: 0.18.0
>
>         Attachments: PIG-3864-1.patch
>
>
> When using ToDate with a location based timezone (e.g. "Europe/Berlin") the handling of the timezone offset is based on whether the timezone is currently in daylight saving and not based on whether the timestamp is in daylight saving time or not.
> Example:
> {noformat}
> B = FOREACH A GENERATE ToDate('2014-02-02 18:00:00.000Z', 'yyyy-MM-dd HH:mm:ss.SSSZ', 'Europe/Berlin') AS Timestamp;
> {noformat}
> This yields 
> {noformat}2014-02-02 20:00:00.000+02{noformat}
> when called during daylight saving in Europe/Berlin although I would expect 
> {noformat}2014-02-02 19:00:00.000+01{noformat}
> During standard time In Europe/Berlin, the above call yields 
> {noformat}2014-02-02 19:00:00.000+01{noformat}
> In Europe/Berlin DST started on March 30th, 2014.
> This seems pretty strange to me. If it is on purpose it should at least be noted in the documentation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)