Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/20839
Yea, I agree that the warn way is the min fix. I actually attempted a try
to fix this locally before and failed to make a clean fix, and I understand the
complexity here, in particular, because of compatibility between Python 2 and
Python 3.
I also took a look for `six` and `python-future` to wrap and reraise the
exceptions in Python 2. The implementation of `six` was missing and
implementation of `python-future` was incomplete.
Also, I took a look for the complexity you mentioned when I initially
proposed the changes in this logic. Looked not quite easy to wrap it manually
too.
Only one main concern is, if it makes sense to call it a warn because the
message contains, for example, the warning message would contain:
```python
...
"'spark.sql.execution.arrow.enabled' is set to
true; however, "
"failed unexpectedly:\n %s\n"
...
```
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
