This has been asked multiple times by a lot of folks - like MRUnit and PigUnit, etc.
+1 On Thu, Apr 2, 2015 at 3:04 AM, Karan Kumar <[email protected]> wrote: > Hi Falcon dev > > As falcon has a bunch of handcrafted xmls ,this results in manual errors > such as typos, giving bad arguments, xml errors etc while deploying a new > job. > For validating the xmls as well as checking the job is getting the correct > set of configs, a mock run is needed in a full fledged setup of > falcon/hadoop/oozie. This I feel is a overkill. > > I propose that we start work on falcon unit which will intialize > falcon/hadoop/oozie in local mode and run the job locally to test the > configs and also can be extended to validate input and output datesets. > This will really help in easily onboarding to falcon jobs as in a matter of > minutes u can test your process. > > Have created a task on jira: > https://issues.apache.org/jira/browse/FALCON-1133 > > Willing to take this up if the community thinks it will add value. > Thoughts? > > Thanks > Karan > -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry
