[ https://issues.apache.org/jira/browse/OOZIE-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira updated OOZIE-1612: -------------------------------- Attachment: OOZIE-1612.3.patch Fixed the issue with long lines. Not touching any unit-tests. AFAIK, log messages are not typically unit tested. > When printing Dates to log messages, we should make sure they are in > oozie.processing.timezone > ---------------------------------------------------------------------------------------------- > > Key: OOZIE-1612 > URL: https://issues.apache.org/jira/browse/OOZIE-1612 > Project: Oozie > Issue Type: Improvement > Affects Versions: trunk > Reporter: Robert Kanter > Priority: Minor > Labels: newbie > Attachments: OOZIE-1612.1.patch, OOZIE-1612.3.patch, > OOZIE-1612.patch, oozie-1612.2.patch > > > We were recently looking into an issue and noticed that the same log message > had printed different date objects with different timezones, which makes it > hard to compare the two. Which leads to the bigger picture, which is that we > should be printing any Date objects in log messages with the > {{oozie.processing.timezone}} timezone (there's a method for that in > {{DateUtils}}). -- This message was sent by Atlassian JIRA (v6.1#6144)