Is start=2014-10-01T00:00Z the coord start or output dataset start? Whats the value of coord start, coord frequency and output dataset start?
On Tue, Dec 16, 2014 at 3:16 AM, J. McConnell <[email protected]> wrote: > > I wonder if anyone could help point me in the best direction to diagnose > this issue. I'm working on a new job that will take as input a month's > worth of hourly data and output a result for that month. The input data is > being resolved correctly, but I can't get the output instance to be > resolved correctly. My output dataset is defined as: > > <datasets> > ... > <dataset name="output" frequency="${coord:months(1)}" > initial-instance="${initialOutputInstance}" timezone="US/Mountain"> > > > <uri-template>${nameNode}/user/${runtimeUser}/${outputBaseDir}/${YEAR}/${MONTH}</uri-template> > </dataset> > </datasets> > > My output event is defined as: > > <output-events> > <data-out name="output" dataset="output"> > <instance>${coord:current(-1)}</instance> > </data-out> > </output-events> > > With a start date of: > > start=2014-10-01T00:00Z > > This results in an output path of: > > hdfs://namenode:8020/output/path/2014/08 > > I expected 2014/09 (I am correctly getting all of September's data as > inputs). The truly confusing thing is that, if I instead ask for > ${coord:current(0)} for the output instance, the result is 2014/10. So, it > jumps from August to October. > > Has anyone seen behavior like this? If not, does anyone have any > suggestions where I can look to determine what is going on? > > Thank you in advance for whatever help you can provide, > > - J. > > -- > J. McConnell > Founder, Übermensch Consulting > -- _____________________________________________________________ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
