Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/9287
I ~guess~ the reason it wasn't accepted and reviewed due to the lack of man
power of committers or the lack of appealing or because it simply just got
stale. At least, I said +1 for this reason.
I ~think~ it is okay to reopen, fix the codes to pass the tests, then keep
pining reviewers after filling the PR description with a proper title according
to the glide lines and an email to dev mailing list, yelling to the public to
explain why this fix is right and nedded. Usually, it is really hard for a lot
of changes to be merged quickly because it is hard to review. For this reason,
I also have several old PRs but I am trying to explain and keep pinging with
rebasing everytime they get conflicts
This one is not really in my area but if you strongly think this is the
right fix and the important change, I'd keep open this and then try to
persuade reviwers with keeping pininging.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
