Github user kellyzly commented on the pull request:
https://github.com/apache/spark/pull/4491#issuecomment-77786385
@srowen,@tgravescs,@vanzin: Encrypted shuffle can make the process of
shuffle more safer. I think it is necessary in spark. Previous design is
reusing hadoop encrypted shuffle algorithm to enable spark encrypted shuffle.
The design has a big problem that it imports many crypto classes like
CryptoInputStream and CryptoOutputStream which is marked "private" in hadoop.
Now my teammates and i decided to write the crypto classes in spark so no
dependance to hadoop 2.6. Not directly copying hadoop code to spark, we only
reference the crypto algorithm like JCE/AES-NI which is used in hadoop. Maybe i
need rename the jira name from "Reuse hadoop encrypted shuffle algorithm to
enable spark encrypted shuffle" to "Add encrypted shuffle in spark". Any
advices are welcome.
---
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]
