From 6f9adf9e908ef1c6a1c5bab345f337ce5c332897 Mon Sep 17 00:00:00 2001 From: Haejoon Lee Date: Tue, 5 Dec 2023 12:29:27 +0900 Subject: [PATCH 1/4] [SPARK-46259][PYTHON][DOCS] Add appropriate link for error class usage documentation. --- python/docs/source/development/contributing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/python/docs/source/development/contributing.rst b/python/docs/source/development/contributing.rst index ad61ba95d695..3eddddabb96c 100644 --- a/python/docs/source/development/contributing.rst +++ b/python/docs/source/development/contributing.rst @@ -246,9 +246,9 @@ To throw a standardized user-facing error or exception, developers should specif Usage ~~~~~ -1. Check if an appropriate error class already exists in `error_classes.py`. +1. Check if an appropriate error class already exists in `Error classes in PySpark `_. If true, use the error class and skip to step 3. -2. Add a new class to `error_classes.py`; keep in mind the invariants below. +2. Add a new class to `error_classes.py `_; keep in mind the invariants below. 3. Check if the exception type already extends `PySparkException`. If true, skip to step 5. 4. Mix `PySparkException` into the exception. From 5db5be49c6ed43d822a4ae2edcf0da550cb711e6 Mon Sep 17 00:00:00 2001 From: Haejoon Lee Date: Tue, 5 Dec 2023 12:53:27 +0900 Subject: [PATCH 2/4] Retrigger CI From 5fe045c040433094d1f44d955c4550c9a7eb0ade Mon Sep 17 00:00:00 2001 From: Haejoon Lee Date: Tue, 5 Dec 2023 13:46:35 +0900 Subject: [PATCH 3/4] Retrigger CI From f844f3b5cd24f6074ffdddc9b1ed8a6ee99540a0 Mon Sep 17 00:00:00 2001 From: Haejoon Lee Date: Tue, 5 Dec 2023 14:36:13 +0900 Subject: [PATCH 4/4] Retrigger again