Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14299
You also should file a bug and reference it from the PR title.
---
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
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/14299
@thunterdb Copy that, working on it and sorry for the acknowledge delay.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user thunterdb commented on the issue:
https://github.com/apache/spark/pull/14299
@AnthonyTruchet thank you for the PR. This is definitely worth fixing for
large deployments. Now, as you noticed, this portion of code does not quite
abide by the best engineering practices...
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/14299
@pzz2011 Nothing _that_ bad if your application is just learning once and
saving / using the embeddings. But if you run hundreds or thousands of
learning, you'll just crash because of
Github user pzz2011 commented on the issue:
https://github.com/apache/spark/pull/14299
@AnthonyTruchet ãIf not Ensure broadcasted variables destoryed, what
will happend?(this is my person confusion:)
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14299
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
