cloud-fan commented on PR #37916:
URL: https://github.com/apache/spark/pull/37916#issuecomment-1251888183

   @dongjoon-hyun @viirya @HyukjinKwon The new error class name prefix 
`_LEGACY_ERROR_TEMP_` proposed here kind of marks the error as 
developer-facing, not user-facing. Developers can still get the error class 
programmatically via the `SparkThrowable` interface, so that they can build 
error infra with it. End users won't see the error class in the message. This 
allows us to do the error migration very quickly, and we can refine the error 
classes and mark them as user-facing later (naming them properly, adding tests, 
etc.). What do you think?


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to