Github user victor-wong commented on the issue:
https://github.com/apache/spark/pull/17782
@srowen
Thanks for replying. I tested with master branch and it turned out the
issue still existed.
I create a new PR against master branch,
https://github.com/apache/spark/pull/17937.
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17782
@victor-wong we wouldn't merge a change just to 1.6, if something else
fixed it in master. You could investigate back-porting whatever fixed it into
1.6, though I doubt there will be more 1.6
Github user victor-wong commented on the issue:
https://github.com/apache/spark/pull/17782
@jerryshao
Sorry for replying late. This issue does exist in master branch as I
described in https://issues.apache.org/jira/browse/SPARK-19688.
What should I do to elaborate more about
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17782
@victor-wong are you going to submit PR for branch-1.6, does this issue
exist in master branch? Also would you please elaborate more about this issue,
thanks.
---
If your project is set up for
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17782
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
