karenfeng commented on a change in pull request #32850:
URL: https://github.com/apache/spark/pull/32850#discussion_r655594657
##########
File path: core/src/main/resources/error/README.md
##########
@@ -0,0 +1,79 @@
+# Guidelines
+
+To throw a standardized exception, developers should use an error class and
message parameters
+rather than an arbitrary error message.
+
+## Usage
+
+To throw an exception, do the following.
+
+1. Check if an appropriate error class already exists in `error-class.json`.
Review comment:
Today, the error messages thrown from Spark are distributed across the
entire code base with no single source of truth - as a result, it is hard to
audit error message for quality and redundancy. With error classes, I'm hoping
that we can improve the auditing process. However, I do recognize that the
number of error classes will likely grow quickly, and that maintaining a high
level of quality will require vigilant pruning. What do you think will help
reduce the burden here?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
