spark 3.2.1 源码下载

# Guidelines To throw a standardized user-facing error or exception, developers should specify the error class and message parameters rather than an arbitrary error message. ## Usage 1. Check if an appropriate error class already exists in `error-class.json`. If true, skip to step 3. Otherwise, continue to step 2. 2. Add a new class to `error-class.json`; keep in mind the invariants below. 3. Check if the exception type already extends `SparkThrowable`. If true, skip to step 5. Otherwise, continue to step 4. 4. Mix `SparkThrowable` into the exception. 5. Throw the exception with the error class and message parameters. ### Before Throw with arbitrary error message: throw new TestException("Problem A because B") ### After `error-class.json` "PROBLEM_BECAUSE": { "message": ["Problem %s because %s"], "sqlState": "XXXXX" } `SparkException.scala` class SparkTestException( errorClass: String, messageParameters: Seq[String]) extends TestException(SparkThrowableHelper.getMessage(errorClass, messageParameters)) with SparkThrowable { def getErrorClass: String = errorClass def getMessageParameters: Array[String] = messageParameters def getSqlState: String = SparkThrowableHelper.getSqlState(errorClass) } Throw with error class and message parameters: throw new SparkTestException("PROBLEM_BECAUSE", Seq("A", "B")) ## Access fields To access error fields, catch exceptions that extend `org.apache.spark.SparkThrowable` and access - Error class with `getErrorClass` - SQLSTATE with `getSqlState` try { ... } catch { case e: SparkThrowable if Option(e.getSqlState).forall(_.startsWith("42")) => warn("Syntax error") } ## Fields ### Error class Error classes are a succinct, human-readable representation of the error category. #### Invariants - Unique - Consistent across releases - Sorted alphabetically ### Message Error messages provide a descriptive, human-readable representation of the error. The message format accepts string parameters via the C-style printf syntax. The quality of the error message should match the [guidelines](https://spark.apache.org/error-message-guidelines.html). #### Invariants - Unique ### SQLSTATE SQLSTATE is an optional portable error identifier across SQL engines. For consistency, Spark only sets SQLSTATE as defined in the ANSI/ISO standard. SQLSTATE comprises a 2-character class value followed by a 3-character subclass value. Spark only uses the standard-defined classes and subclasses, and does not use implementation-defined classes or subclasses. #### Invariants - Consistent across releases #### ANSI/ISO standard The following SQLSTATEs are from ISO/IEC CD 9075-2. |SQLSTATE|Class|Condition |Subclass|Subcondition | |--------|-----|------------------------------------------------------------|--------|---------------------------------------------------------------| |07000 |07 |dynamic SQL error |000 |(no subclass) | |07001 |07 |dynamic SQL error |001 |using clause does not match dynamic parameter specifications | |07002 |07 |dynamic SQL error |002 |using clause does not match target specifications | |07003 |07 |dynamic SQL error |003 |cursor specification cannot be executed | |07004 |07 |dynamic SQL error |004 |using clause required for dynamic parameters | |07005 |07 |dynamic SQL error |005 |prepared statement not a cursor specification | |07006 |07 |dynamic SQL error |006 |restricted data type attribute violation | |07007 |07 |dynamic SQL error |007 |using clause required for result fields | |07008 |07 |dynamic SQL error |008 |invalid descriptor count | |07009 |07 |dynamic SQL error |009 |invalid descriptor index | |0700B |07 |dynamic SQL error |00B |data type transform function violation | |0700C |07 |dynamic SQL error |00C |undefined DATA value | |0700D |07 |dynamic SQL error |00D |invalid DATA target | |0700E |07 |dynamic SQL error |00E |invalid LEVEL value | |0700F |07 |dynamic SQL error |00F |invalid DATETIME_INTERVAL_CODE | |08000 |08 |connection exception |000 |(no subclass) | |08001 |08 |connection exception |001 |SQL-client unable to establish SQL-connection | |08002 |08 |connection exception |002 |connection name in use | |08003 |08 |connection exception |003 |connection does not exist | |08004 |08 |connection exception |004 |SQL-server rejected establishment of SQL-connection | |08006 |08 |connection exception |006 |connection failure | |08007 |08 |connection exception |007 |transaction resolution unknown | |09000 |09 |triggered action exception |000 |(no subclass) | |0A000 |0A |feature not supported |000 |(no subclass) | |0A001 |0A |feature not supported |001 |multiple server transactions | |0D000 |0D |invalid target type specification |000 |(no subclass) | |0E000 |0E |invalid schema name list specification |000 |(no subclass) | |0F000 |0F |locator exception |000 |(no subclass) | |0F001 |0F |locator exception |001 |invalid specification | |0L000 |0L |invalid grantor |000 |(no subclass) | |0M000 |0M |invalid SQL-invoked procedure reference |000 |(no subclass) | |0P000 |0P |invalid role specification |000 |(no subclass) | |0S000 |0S |invalid transform group name specification