Awesome, thanks Matt! -- Chris
On Thu, Apr 4, 2013 at 10:34 AM, Matt Goeke <[email protected]> wrote: > Yes, you can purge based on the time property built into the server OR > through SQL. > > We do a lot of pruning just by using SQL/ODBC directly against the backend > schema to keep the console usable. The below set of statements are an > example of iteratively deleting all data related to a specific > coordinatorID: > > delete from oozie.WF_ACTIONS where wf_id in (select id from oozie.WF_JOBS > where id in (select external_id from oozie.COORD_ACTIONS where job_id in > (select id from oozie.COORD_JOBS where id=""))); > delete from oozie.WF_JOBS where id in (select external_id from > oozie.COORD_ACTIONS where job_id in (select id from oozie.COORD_JOBS where > id="")); > delete from oozie.COORD_ACTIONS where job_id in (select id from > oozie.COORD_JOBS where id='"); > delete from oozie.COORD_JOBS where id=""; > > Doing a manual purge using less stringent criteria is even easier: > > delete all from oozie.WF_ACTIONS; > delete all from oozie.WF_JOBS; > > etc... > > -- > Matt > > > On Thu, Apr 4, 2013 at 9:01 AM, Chris Sigman <[email protected]> wrote: > >> At the moment, just job history >> >> -- >> Chris >> >> >> On Thu, Apr 4, 2013 at 9:34 AM, Matt Goeke <[email protected]> >> wrote: >> > Chris, >> > >> > Really not sure what you are asking without a little more context. Is >> this >> > related to staged coordinators / bundles meta or is this about job >> history >> > and root Oozie server configs? >> > >> > -- >> > Matt >> > >> > >> > On Thu, Apr 4, 2013 at 6:56 AM, Chris Sigman <[email protected]> wrote: >> > >> >> Is there a way to manually execute a purge, i.e. without shutting down >> >> the server, changing the conf as needed, restarting, reverting the >> >> conf and restarting again? >> >> >> >> Thanks! >> >> -- >> >> Chris >> >> >>
