Github user zhaorongsheng commented on the pull request:
https://github.com/apache/spark/pull/13118#issuecomment-219288567
sorry, it is unintentional mistake.
I close it right now!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user zhaorongsheng closed the pull request at:
https://github.com/apache/spark/pull/13118
---
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 feature
enabled and wishes so, or if the feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13118#issuecomment-219223888
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 p
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13118#issuecomment-219223860
@zhaorongsheng it seems it is open mistakenly. I guess this might have to
be closed.
---
If your project is set up for it, you can reply to this email and have you
GitHub user zhaorongsheng opened a pull request:
https://github.com/apache/spark/pull/13118
update from orign
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explai
