srielau commented on PR #58282: URL: https://github.com/apache/spark/pull/58282#issuecomment-5499202927
@nchammas Unnesting is of course always an option. That however leads not only to an explosion of error conditions, it also leads to an explosion of conditions to be caught by condition handlers. Today condition handlers can collapse conditions by either filtering by SQLSTATE, or by naming the top level condition without subclass. The later is one of the appeals of using subclasses for different flabvors of the "same" condition. You pointed out some of the more hilarious abhorations already. Can you explain why simply allowing an exception to not use a subclass if none apply, is bad? I am assuming good faith taht developers with add subclasses if there should be one added, and they won't abuse this new found option to just generalize. -- 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]
