Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14827
OK that makes sense as a reason to have 2.7 vs <2.6. We already have a
profile for 2.7 anyway. I don't know if it will help to make it active by
default here given how profile activation works.
Bumping to 2.7.3 is fine. But do you perhaps mean to suggest we bump the
default Hadoop profile up? to 2.6, 2.7 even? that would really be a change to
how the release is built, and how the PR builders run.
If we're doing that, it's worth asking: what's the cost/benefit of
supporting <2.6 anyway? I think all the major distros are on at least 2.6 for
like 2 years. EMR is on 2.7. CDH is the laggard if anything being on 2.6 + a
large number of patches towards 2.7.
It would let us undo a mild bit of reflection hackery in the code and more
freely use Hadoop APIs. We'd get rid of loads of build profiles too, hey.
I would not mind hijacking your issue and turning it into this question
instead.
Whether it makes sense to start pulling in hadoop-aws etc is a different
question.
---
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]
