Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SPARK-46241][PYTHON][CONNECT] Fix error handling routine so it would…
…n't fall into infinite recursion ### What changes were proposed in this pull request? Remove _display_server_stack_trace and always display error stack trace if we have one ### Why are the changes needed? There is a certain codepath which can make existing error handling fall into infinite recursion. I.e. consider following codepath: `[Some error happens] -> _handle_error -> _handle_rpc_error -> _display_server_stack_trace -> RuntimeConf.get -> SparkConnectClient.config -> [An error happens] -> _handle_error`. There can be other similar codepaths ### Does this PR introduce _any_ user-facing change? Gets rid of occasionally infinite recursive error handling (which can cause downgraded user experience) ### How was this patch tested? N/A ### Was this patch authored or co-authored using generative AI tooling? No Closes apache#44144 from cdkrot/forbid_recursive_error_handling. Authored-by: Alice Sayutina <alice.sayutina@databricks.com> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
- Loading branch information