[ https://issues.apache.org/jira/browse/SPARK-22634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575066#comment-16575066 ]
Sean Owen commented on SPARK-22634: ----------------------------------- That text is part of Netty's NOTICE file, which must be reproduced, but, it isn't actually pulled in by Netty according to mvn. It says only jets3t uses it, and you say jets3t isn't used directly here. I'd say this is resolved if SPARK-23654 is resolved then. There's another reason to remove this if it's not necessary. Being crypto software, I think we need to update an ECCN for Spark if it's distributed. I'm investigating that separately. But all the better to remove it if not needed. > Update Bouncy castle dependency > ------------------------------- > > Key: SPARK-22634 > URL: https://issues.apache.org/jira/browse/SPARK-22634 > Project: Spark > Issue Type: Task > Components: Spark Core, SQL, Structured Streaming > Affects Versions: 2.2.0 > Reporter: Lior Regev > Assignee: Sean Owen > Priority: Minor > Fix For: 2.3.0 > > > Spark's usage of jets3t library as well as Spark's own Flume and Kafka > streaming uses bouncy castle version 1.51 > This is an outdated version as the latest one is 1.58 > This, in turn renders packages such as > [spark-hadoopcryptoledger-ds|https://github.com/ZuInnoTe/spark-hadoopcryptoledger-ds] > unusable since these require 1.58 and spark's distributions come along with > 1.51 > My own attempt was to run on EMR, and since I automatically get all of > spark's dependecies (bouncy castle 1.51 being one of them) into the > classpath, using the library to parse blockchain data failed due to missing > functionality. > I have also opened an > [issue|https://bitbucket.org/jmurty/jets3t/issues/242/bouncycastle-dependency] > with jets3t to update their dependecy as well, but along with that Spark > would have to update it's own or at least be packaged with a newer version -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org