You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/06/18 20:23:43 UTC
[jira] [Commented] (OOZIE-649) Fail fast when a date doesn't parse
correctly
[ https://issues.apache.org/jira/browse/OOZIE-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396104#comment-13396104 ]
Alejandro Abdelnur commented on OOZIE-649:
------------------------------------------
+1 Robert, looks good, using setLenient(false) makes the fix much simpler.
> 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
> Assignee: Robert Kanter
> Priority: Minor
> Attachments: 649-v1.txt, 649.patch
>
>
> 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