> On 2011-12-05 21:32:37, Santhosh Srinivasan wrote: > > Some code formatting and error message comments. The test coverage has to > > be improved.
I forgot to add my most important comment. This code fix will break backward compatibility, i.e., what used to work before will now fail. Are there any options to mitigate the impact to existing users? - Santhosh ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/3018/#review3636 ----------------------------------------------------------- On 2011-12-05 20:15:04, Mona Chitnis wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/3018/ > ----------------------------------------------------------- > > (Updated 2011-12-05 20:15:04) > > > Review request for oozie, Mohammad Islam and Angelo K. Huang. > > > Summary > ------- > > For the coordinator input events, if there are multiple dates, it uses the > first date to resolve the data > instance, instead of giving warning or error. > For example: > <data-in name="din1" dataset="ds1"> > <instance>2010-06-11T00:30Z,2010-06-11T00:31Z,2010-06-11T00:32Z</instance> > </data-in> > > Similarly for output events. > > This patch will give error for the above case and protect against submission > of job that defaults to the first date without the knowledge of user. > > > This addresses bug OOZIE-15. > https://issues.apache.org/jira/browse/OOZIE-15 > > > Diffs > ----- > > > trunk/core/src/main/java/org/apache/oozie/command/coord/CoordSubmitXCommand.java > 1209756 > > trunk/core/src/test/java/org/apache/oozie/command/coord/TestCoordSubmitXCommand.java > 1209756 > > Diff: https://reviews.apache.org/r/3018/diff > > > Testing > ------- > > yes > > > Thanks, > > Mona > >
