Thanks for pointing this out, Nicholas. This SPIP seems focused on the Scala side, grouping the exception handling and providing some guidance about error messages. Yes, I think we can refer to it on the PySpark side. Probably I will follow up and file some JIRAs based on how this SPIP gose, and run it separately. BTW, it’s slightly different from SPARK-32194 <https://issues.apache.org/jira/browse/SPARK-32194> because this JIRA targets to have a set of proper classes instead of, for example, just plain Exception.
2020년 10월 26일 (월) 오전 10:36, Nicholas Chammas <nicholas.cham...@gmail.com>님이 작성: > Just want to call out that this SPIP should probably account somehow for > PySpark and the work being done in SPARK-32082 > <https://issues.apache.org/jira/browse/SPARK-32082> to improve PySpark > exceptions. > > On Sun, Oct 25, 2020 at 8:05 PM Xinyi Yu <xyy...@gmail.com> wrote: > >> Hi all, >> >> We like to post a SPIP of Standardize Exception Messages in Spark. Here is >> the document link: >> >> https://docs.google.com/document/d/1XGj1o3xAFh8BA7RCn3DtwIPC6--hIFOaNUNSlpaOIZs/edit?usp=sharing >> < >> https://docs.google.com/document/d/1XGj1o3xAFh8BA7RCn3DtwIPC6--hIFOaNUNSlpaOIZs/edit?usp=sharing> >> >> >> This SPIP aims to standardize the exception messages in Spark. It has >> three >> major focuses: >> 1. Group exception messages in dedicated files for easy maintenance and >> auditing. >> 2. Establish an error message guideline for developers. >> 3. Improve error message quality. >> >> Thanks for your time and patience. Looking forward to your feedback! >> >> >> >> -- >> Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/ >> >> --------------------------------------------------------------------- >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >> >>
