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 AA9A4200D0F for ; Fri, 15 Sep 2017 03:35:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A94431609CE; Fri, 15 Sep 2017 01:35:09 +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 EEE121609CD for ; Fri, 15 Sep 2017 03:35:08 +0200 (CEST) Received: (qmail 43735 invoked by uid 500); 15 Sep 2017 01:35:08 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 43724 invoked by uid 99); 15 Sep 2017 01:35:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Sep 2017 01:35:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8373FC5898 for ; Fri, 15 Sep 2017 01:35:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id F_MiZ5MfrGnJ for ; Fri, 15 Sep 2017 01:35:06 +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 432D65FB4E for ; Fri, 15 Sep 2017 01:35:06 +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 5C4BEE0EAC for ; Fri, 15 Sep 2017 01:35:04 +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 5709425387 for ; Fri, 15 Sep 2017 01:35:02 +0000 (UTC) Date: Fri, 15 Sep 2017 01:35:02 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7162) Remove XML excludes file format MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 15 Sep 2017 01:35:09 -0000 [ https://issues.apache.org/jira/browse/YARN-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167210#comment-16167210 ] Junping Du commented on YARN-7162: ---------------------------------- bq. Given that code freeze for Hadoop 3 beta 1 is tomorrow (Sept 15), perhaps we should compromise by removing this for now from branch-3.0 but leave it in trunk, and revisit this for 3.1.0? +1. This sounds more reasonable. We may revisit this a couple of month from now to see what to do for XML format. > Remove XML excludes file format > ------------------------------- > > Key: YARN-7162 > URL: https://issues.apache.org/jira/browse/YARN-7162 > Project: Hadoop YARN > Issue Type: Sub-task > Components: graceful > Affects Versions: 2.9.0, 3.0.0-beta1 > Reporter: Robert Kanter > Assignee: Robert Kanter > Priority: Blocker > Attachments: YARN-7162.001.patch, YARN-7162.branch-2.001.patch > > > YARN-5536 aims to replace the XML format for the excludes file with a JSON format. However, it looks like we won't have time for that for Hadoop 3 Beta 1. The concern is that if we release it as-is, we'll now have to support the XML format as-is for all of Hadoop 3.x, which we're either planning on removing, or rewriting using a pluggable framework. > [This comment in YARN-5536|https://issues.apache.org/jira/browse/YARN-5536?focusedCommentId=16126194&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16126194] proposed two quick solutions to prevent this compat issue. In this JIRA, we're going to remove the XML format. If we later want to add it back in, YARN-5536 can add it back, rewriting it to be in the pluggable framework. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org