You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Steve Hoffman (JIRA)" <ji...@apache.org> on 2013/09/30 18:45:24 UTC

[jira] [Updated] (FLUME-2201) 2 forms of timezone not supported by RFC5424 implementation

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

Steve Hoffman updated FLUME-2201:
---------------------------------

    Affects Version/s: v1.2.0
                       v1.3.0
                       v1.4.0

> 2 forms of timezone not supported by RFC5424 implementation
> -----------------------------------------------------------
>
>                 Key: FLUME-2201
>                 URL: https://issues.apache.org/jira/browse/FLUME-2201
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v1.2.0, v1.3.0, v1.4.0
>            Reporter: Steve Hoffman
>
> The SyslogUtils implementation of RFC 5424 is using this regular expression for matching the ISO8601 time:
> {code}
>       "(?:(\\d{4}[-]\\d{2}[-]\\d{2}[T]\\d{2}[:]\\d{2}[:]\\d{2}(?:\\.\\d{1,6})?(?:[+-]\\d{2}[:]\\d{2}|Z)?)|-)" + // stamp
> {code}
> According to http://en.wikipedia.org/wiki/ISO_8601#Time_zone_designators there are 4 possible forms:
> * Z
> * +/-hh:mm
> * +/-hhmm
> * +/-hh
> This regex only supports the first 2.  I discovered this when a message used the 3rd form and wound up with strange output and dates all over the place (even thought the input was all from the same general time range).



--
This message was sent by Atlassian JIRA
(v6.1#6144)