[
https://issues.apache.org/jira/browse/OOZIE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186270#comment-13186270
]
Jeremy Hanna commented on OOZIE-649:
------------------------------------
playing with the SimpleDateFormat.parse method, it is really lenient and tries
to make do with what it is given rather than throw an error. For example the
15th month of the year just translates to March of the next year. I tried it
with the built-in DateUtils. Probably easiest to validate it there. I'll see
if there's any lib that just does that, otherwise I'll attach a patch to do
some simple validation in that util class.
> Fail fast when a date doesn't parse correctly
> ---------------------------------------------
>
> Key: OOZIE-649
> URL: https://issues.apache.org/jira/browse/OOZIE-649
> Project: Oozie
> Issue Type: Improvement
> Reporter: Jeremy Hanna
> Priority: Minor
>
> We had an instance where we had an obviously invalid start date for a
> coordinator job - 2011-12-287T01:00Z - note it will start on the 287th day of
> December. I checked on the job today to see if the jobs were completing and
> it said it was still in PREP. I double checked the start date and sure
> enough, it wasn't yet December 287th :). It would be nice to fail fast so
> that the error can be addressed sooner. I would imagine it would just be a
> date validator and an error thrown when trying to launch the coordinator. I
> can submit a patch - if someone would like to just point me in the right
> direction as far as where to get to the job submission code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
