Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37120178CA for ; Thu, 14 May 2015 18:57:01 +0000 (UTC) Received: (qmail 27879 invoked by uid 500); 14 May 2015 18:57:01 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 27840 invoked by uid 500); 14 May 2015 18:57:01 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 27802 invoked by uid 99); 14 May 2015 18:57:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2015 18:57:00 +0000 Date: Thu, 14 May 2015 18:57:00 +0000 (UTC) From: "Jonathan Eagles (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544192#comment-14544192 ] Jonathan Eagles commented on YARN-3624: --------------------------------------- This change solves this issue where users have specified a specific order of filter initializers in the config. The application history server then reorders the the timeline authentication initializer to be at the front of the list. This breaks users who are using web cookie-based login systems that require being run before timeline authentication. [~zjshen], do you see any issues with this change. Can you see anyone relying on the current behavior where initializers are reordered? > ApplicationHistoryServer reverses the order of the filters it gets > ------------------------------------------------------------------ > > Key: YARN-3624 > URL: https://issues.apache.org/jira/browse/YARN-3624 > Project: Hadoop YARN > Issue Type: Bug > Components: timelineserver > Affects Versions: 2.6.0 > Reporter: Mit Desai > Assignee: Mit Desai > Attachments: YARN-3624.patch > > > AppliactionHistoryServer should not alter the order in which it gets the filter chain. Additional filters should be added at the end of the chain. -- This message was sent by Atlassian JIRA (v6.3.4#6332)