Github user sethah commented on the issue:
https://github.com/apache/spark/pull/13959
The lack of bandwidth in MLlib means that sometimes good code that would
make an impact just gets ignored. This is kind of the reality of things.
However, if we are going to close the PR simply because committers could not or
did not get to it - this is the case here IMO - then we should also close the
JIRA. Closing a PR for this reason essentially means "we don't see this as an
issue worth spending time on." That's a reason to close a JIRA as well. Closing
the JIRA will at least prevent others from wasting their time on this issue
like @MechCoder did.
If we don't close the JIRA, then it seems like we are closing it merely
because we don't want the "clutter" of long waiting prs. But if a PR is still
valid, well-written, and solves a real problem, why would we not keep it open?
This sends a bad message to contributors IMO.
---
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
