Github user dataknocker commented on the issue:
https://github.com/apache/spark/pull/18262
Some thing wrong, so I close this pr and add new pr
[#18324](https://github.com/apache/spark/pull/18324)
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18262
cc @viirya here too. (This one is similar one with few PRs you and I are
reviewing).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user dataknocker commented on the issue:
https://github.com/apache/spark/pull/18262
@HyukjinKwon ok, I will add my test later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18262
@dataknocker, probably, you are able to add a test something like this:
```python
def e1():
raise Exception(u"ì".encode("UTF-8"))
spark.sparkContext.parallelize([1]
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18262
Also, I think we need a small test to check if it really fixes the problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user dataknocker commented on the issue:
https://github.com/apache/spark/pull/18262
We can choose one pr in this and
[#18261](https://github.com/apache/spark/pull/18261) to slove SPARK-21045
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18262
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
