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 8C6FB200BB8 for ; Sat, 12 Nov 2016 20:55:42 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8B1FF160B00; Sat, 12 Nov 2016 19:55:42 +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 D533E160AF5 for ; Sat, 12 Nov 2016 20:55:41 +0100 (CET) Received: (qmail 36771 invoked by uid 500); 12 Nov 2016 19:55:41 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 36762 invoked by uid 99); 12 Nov 2016 19:55:41 -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; Sat, 12 Nov 2016 19:55:41 +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 9F8021A00D8 for ; Sat, 12 Nov 2016 19:55:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -7.018 X-Spam-Level: X-Spam-Status: No, score=-7.018 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] 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 q4lw5QXy0PHa for ; Sat, 12 Nov 2016 19:55:38 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 931315F570 for ; Sat, 12 Nov 2016 19:55:37 +0000 (UTC) Received: (qmail 36640 invoked by uid 99); 12 Nov 2016 19:55:23 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Nov 2016 19:55:23 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 6E911E0158; Sat, 12 Nov 2016 19:55:23 +0000 (UTC) From: uce To: issues@flink.incubator.apache.org Reply-To: issues@flink.incubator.apache.org Message-ID: Subject: [GitHub] flink pull request #2795: Revert "[FLINK-4913][yarn] include user jars in sy... Content-Type: text/plain Date: Sat, 12 Nov 2016 19:55:23 +0000 (UTC) archived-at: Sat, 12 Nov 2016 19:55:42 -0000 GitHub user uce opened a pull request: https://github.com/apache/flink/pull/2795 Revert "[FLINK-4913][yarn] include user jars in system class loader" In general, a very good fix imo, but it is part of RC1 for 1.1.4. It might be better to exclude it for the bug fix release since it changes class loading behaviour between minor version. This could possibly lead to hard to debug `Cannot cast class A to A exceptions` if a user relies on loading classes via the user code loader which are available via the system class loader with this commit. You can merge this pull request into a Git repository by running: $ git pull https://github.com/uce/flink 4913-revert_yarn_sysclassloader Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/2795.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2795 ---- commit 324ddaed54b138e11fac98b906b78a016f83a24b Author: Ufuk Celebi Date: 2016-11-12T19:49:17Z Revert "[FLINK-4913][yarn] include user jars in system class loader" This reverts commit ea41b9c56fdc0af3c97d6dd48d04218db6176ec8. ---- --- 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 infrastructure@apache.org or file a JIRA ticket with INFRA. ---