I like the idea of consistent messages; it makes understanding errors easier. Having said that, Exception messages themselves are not part of the exposed contract to users; and are subject to change. We should leave that flexibility open to spark developers ... I am currently viewing this proposal as a internal standardization exercise within Spark codebase, and not as a public contract with users. Is that aligned with the objectives ? Or are we looking at this as a public contract to users ? I am not in favour of the latter.
Regards, Mridul On Sun, Oct 25, 2020 at 7: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 > >
