Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Pig Wiki" for change 

The following page has been changed by GuntherHagleitner:

  If pig is launched in interactive mode with this switch "exec" statements are 
also going to run in interactive mode.
+ [[Anchor(Error_Handling)]]
+ === Error Handling ===
+ With multiquery Pig processes an entire script or a batch of statements at 
once. By default Pig tries to run all the jobs
+ that result from that - regardless of whether some jobs fail during 
execution. A user has the following options to check 
+ which jobs have succeeded or failed:
+ Pig logs all successful and failed store commands. Store commands are 
identified by output path. At the end of execution a summary line
+ indicates success, partial failure or failure of all store commands.
+ Pig also returns different code upon completion for these scenarios:
+    * Return code 0: All jobs succeeded
+    * (Return code 1 is used for retriable errors)
+    * Return code 2: All jobs have failed
+    * Return code 3: Some jobs have failed
+ ==== Turning off best effort execution ====
+ In some cases it might be desirable to fail the entire script upon detecting 
the first failed job. This can be achieved with
+ the "-F" or "-stop_on_failure" command line flag. If used, Pig will stop 
execution when the first failed job is detected and 
+ discontinue further processing. This also means that file commands that come 
after a failed store in the script will not be
+ executed (This can be used to create "done" files).
+ This is how the flag is used:
+ {{{
+ $ pig -F foo.pig
+ or:
+ $ pig -stop_on_failure foo.pig
+ }}}
  === Incompatible Changes ===

Reply via email to