Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/11007#issuecomment-178206958
Hi @gabrielenizzoli - generally Spark require's that there is a JIRA
associated the proposed change as well as having it mentioned in the pull
request title. This is also just merging against the 1.6 branch but generally
most changes are applied to master and then explicitly back ported (looking in
master it seems to have changed as part of the migration away from having guava
in the public API to `Optional.ofNullable`). The guide at
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark can be
quite useful for structuring your pull request.
---
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]
