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. `PigParseException` Used for indicating errors due to parsing - 2. `TypeCheckerException` Used for indicating errors due to type checking + 1. `TypeCheckerException` Used for indicating errors due to type checking - 3. `LogicalOptimizerException` Used for indicating errors during logical plan optimization + 1. `LogicalOptimizerException` Used for indicating errors during logical plan optimization - 4. `LogicalToPhysicalTranslatorException` Used for indicating errors during logical plan to physical plan translation + 1. `LogicalToPhysicalTranslatorException` Used for indicating errors during logical plan to physical plan translation - 5. `PhysicalToMRTranslatorException` Used for indicating errors during physical plan to map reduce plan translation + 1. `PhysicalToMRTranslatorException` Used for indicating errors during physical plan to map reduce plan translation - 6. `MRJobCompilerException` Used for indicating errors during map reduce plan compilation + 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. @@ -84, +83 @@ 1. -wagg to turn on warning aggregation; by default warning aggregation is turned off. 2. -v to include printing error messages on screen; by default error messages will be written to client side log. Using -v will also print the messages on the screen - 3. -l directory where the client side log is stored; by default, logs will be stored in the current working directory and named pig_<datestamp>_<pid>.log. When used in batch mode (i.e., when a script to be executed is provided), the log file name will also contain the name of the script - pig_<datestam>_<pig>_<pig_file>.log. + 3. -l directory where the client side log is stored; by default, logs will be stored in the current working directory and named pig_<datestamp>.log. When used in batch mode (i.e., when a script to be executed is provided), the log file name will also contain the name of the script - pig_<datestam>_<pig_file>.log. == Compendium of error messages == @@ -167, +166 @@ == Change Log == - 1. December 19, 2008: Changed the "Compendium of error messages" to include error codes along with updated error messages + 1. December 19, 2008: Changed the "Compendium of error messages" to include error codes along with updated error messages + 1. December 23, 2008: - 2. December 23, 2008: Updated "Compendium of error messages" to include new error codes (2002, 2003, 4000, 4001, 6000, 6001) and error messages and moved error code 1002 to 2001 + i. Updated "Compendium of error messages" to include new error codes (2002, 2003, 4000, 4001, 6000, 6001) and error messages and moved error code 1002 to 2001 - 3. + i. Updated "Frontend errors" to remove PigParseException + i. Updated "Additional command line switches" to remove pid from log file name. == References ==
