Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8C2DE200D48 for ; Wed, 29 Nov 2017 17:09:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8B1C7160C16; Wed, 29 Nov 2017 16:09:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D1913160BF6 for ; Wed, 29 Nov 2017 17:09:05 +0100 (CET) Received: (qmail 29100 invoked by uid 500); 29 Nov 2017 16:09:05 -0000 Mailing-List: contact issues-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@spark.apache.org Received: (qmail 29090 invoked by uid 99); 29 Nov 2017 16:09:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Nov 2017 16:09:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 438911A0123 for ; Wed, 29 Nov 2017 16:09:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id gUgRMY91T0X3 for ; Wed, 29 Nov 2017 16:09:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B35575F576 for ; Wed, 29 Nov 2017 16:09:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id EC70BE0F65 for ; Wed, 29 Nov 2017 16:09:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5B9822105E for ; Wed, 29 Nov 2017 16:09:00 +0000 (UTC) Date: Wed, 29 Nov 2017 16:09:00 +0000 (UTC) From: "Sean Owen (JIRA)" To: issues@spark.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SPARK-22634) Update Bouncy castle dependency MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 29 Nov 2017 16:09:06 -0000 [ https://issues.apache.org/jira/browse/SPARK-22634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271012#comment-16271012 ] Sean Owen commented on SPARK-22634: ----------------------------------- Right, I see core depends on jets3t, so it's not just provided by Hadoop. Looks reasonable, but maybe worth bumping jets3t to 0.9.4 as well; it fixes some bugs and also ups the version of bouncy castle it wants, which may avoid problems with bumping bouncy castle yet further. > 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 > Priority: Minor > > 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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org For additional commands, e-mail: issues-help@spark.apache.org