Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16620
Thanks for all the investigation and the write up, @kayousterhout This
makes good sense to me, and should take us a long way toward both fixing the
immediate bug and improving the code. We should also make sure that our
intentions and understanding get preserved in documentation that is more
obvious and accessible in the future than PR discussion threads. Probably more
comments in the source code that cover the essence of your "very long write
up", but maybe we should consider creating an external documentation page (wiki
or something) that covers in long form what we know and intend; then we can
scale down the in-code comments to a shorter form that includes pointers to the
long form.
---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
