This is awesome! Amusingly enough this was something I had in our private JIRA to work on but we have been too busy trying to production-ize the deployment of our workflows/coordinators. I am curious about something I read on the main github page and will have to see if I can dig through your source soon so feel free to correct me if I am wrong: could using the oozie client for querying be avoided completely by just hitting the schema directly? There is very little I have found I needed to go through the client/CLI for that I couldn't write simple SQL to get.
Either way I commend you guys for open sourcing it and this is extremely helpful! -- Matt On Tue, Oct 16, 2012 at 3:42 PM, Matthew Rathbone <[email protected]>wrote: > Hey guys, > > We just open sourced a small dashboard we use for monitoring our oozie > jobs, thought I'd share: > https://github.com/foursquare/oozie-web > > It originated from a hack-day project here at foursquare with the goal to > make it a little easier to find and link to job detail pages. It's a very > simple web-server that uses the java OozieClient to query for jobs. It's > only built for the CDH3 version of oozie at the moment (2.3.2), but we'll > be updating it soon for cdh4 which is oozie 3.something. > > > Would love opinions and feedback! Having great success with Oozie here at > foursquare. Here's the accompanying blog post: > > http://engineering.foursquare.com/2012/10/16/open-sourcing-our-dashboard-for-apache-oozie/ > > Thanks, > -- > Matthew Rathbone > Foursquare | Software Engineer | Server Engineering Team > [email protected] | @rathboma <http://twitter.com/rathboma> | > 4sq<http://foursquare.com/rathboma> >
