Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16830
Merged to master
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16830
**[Test build #3569 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3569/testReport)**
for PR 16830 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16830
**[Test build #3569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3569/testReport)**
for PR 16830 at commit
Github user dongjinleekr commented on the issue:
https://github.com/apache/spark/pull/16830
Is this exactly corresponds to your intention?
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16830
I don't quite understand the sentence -- it now talks about "T to Writable"?
The change should be one word, and if you would, also improve the
formatting with some back-ticks.
---
If your
Github user dongjinleekr commented on the issue:
https://github.com/apache/spark/pull/16830
Updated with the problem description. Please have a look when you are free.
I will review the other documentation descriptions ...
---
If your project is set up for it, you can reply to this
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16830
You're right about "to" vs "from" but why the word 'restoration'?
'conversion' remains correct. If you would, have a look at improving this and
other docs around it while you're here. For example
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16830
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
