Dear Wiki user,

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

The following page has been changed by SanthoshSrinivasan:
http://wiki.apache.org/pig/PigErrorHandlingFunctionalSpecification

------------------------------------------------------------------------------
  === Frontend errors ===
        The front-end consists of multiple components - parser, type checker, 
optimizer, translators, etc. These errors usually occur at the client side 
before the execution begins in Hadoop. All the errors from these components can 
be categorized as front-end errors. Components that are part of the front end 
will throw specific exceptions that capture the context. For example, the 
parser throws a `ParseException`, the type checker will throw a 
`TypeCheckerException`, the optimizer will throw a `LogicalOptimizerException`, 
etc. A list of the exceptions thrown in the front-end are as follows.
  
+    1. `FrontendException` Generic front-end exception
+    1. `JobCreationException` Used for indicating errors during Map Reduce job 
creation
+    1. `LogicalToPhysicalTranslatorException` Used for indicating errors 
during logical plan to physical plan translation
+    1. `MRCompilerException` Used for indicating errors during map reduce plan 
compilation from physical plan
+    1. `OptimizerException` Used for indicating errors during logical plan 
optimization
+    1. `PigException` Generic exception in Pig
+    1. `PlanException` Used for indicating errors during plan/graph operations
+    1. `PlanValidationException` Used for indicating errors during plan 
validation
+    1. `SchemaMergeException` Used for indicating errors during schema merges
     1. `TypeCheckerException` Used for indicating errors due to type checking
+    1. `VisitorException` Used for indicating errors when visiting a plan
+ 
-    1. `LogicalOptimizerException` Used for indicating errors during logical 
plan optimization
-    1. `LogicalToPhysicalTranslatorException` Used for indicating errors 
during logical plan to physical plan translation
-    1. `PhysicalToMRTranslatorException` Used for indicating errors during 
physical plan to map reduce plan translation
-    1. `MRJobCompilerException` Used for indicating errors during map reduce 
plan compilation
  
  === Backend errors ===
        The execution pipeline, the operators that form the pipeline and the 
map reduce classes fall into the back-end. The errors that occur in the 
back-end are generally at run-time. Exceptions such as `ExecException` and 
`RunTimeException` fall into this category. These errors will be propagated to 
the user facing system and an appropriate error message indicating the source 
of the error will be displayed.
@@ -270, +277 @@

     1. January 14, 2009: Updated "Compendium of error messages" to include new 
error codes (1074, 2052 through 2054, 2098, 2099)
     1. January 21, 2009: Updated "Compendium of error messages" to include new 
error codes (1075, 2055 through 2057)
     1. January 22, 2009: Updated "Compendium of error messages" to include new 
error codes (2058)
+    1. January 23, 2009: Updated "Frontend errors" to update the list of 
exceptions thrown in the front-end.
  
  == References ==
  

Reply via email to