hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets
Date Thu, 14 May 2015 18:57:00 GMT

    [ 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)

Mime
View raw message