Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/10761#issuecomment-213151310
@kevincox right.
- Usually, I believe such changes need a JIRA which manages the issues in
Spark. Usually there sould be a JIRA to discuss a proper way to fix and
problems **before** submitting a PR.
- This seems not following Spark guide lines for contribution,
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark
- It seems not following coding style guide lines,
https://github.com/databricks/scala-style-guide.
- Recently, there was a discussion that there are currently too many PRs
open which makes comitters (or "maintainers") hard to review. Please refer this
link,
http://apache-spark-developers-list.1001551.n3.nabble.com/auto-closing-pull-requests-that-have-been-inactive-gt-30-days-td17208.html
- Most importantly comitters think this should be closed for now. If
contributors want committers respect contributers, then I think contributors
respect them first.
---
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
