juliuszsompolski commented on PR #48882: URL: https://github.com/apache/spark/pull/48882#issuecomment-2483383907
@yaooqinn @cloud-fan Hmm... So I see that it happens in a pattern: The LazyTry of executedPlan triggers the LazyTry of sparkPlan triggers the LazyTry of optimizedPlan triggers the LazyTry of analyzedPlan... So if you get an AnalysisError and then trigger the executedPlan, the stitched together stack trace of exception will be the full stack trace going down into where the error originally happened in the analyzer, stitched with the stack trace of where it got called now... but then each LazyTry layer adds it's own suppressed exception of the full stack trace of where it was called from where it originally happened. I guess I could still do something to see that if an exception already has a `OriginalTryStackTraceException` I could compare if we are within the same recursive call, and don't add it again if so... But I will have to think about it. I won't have time for it this week, let's not merge it until I have a chance to think about it. -- 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: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
