[jira] [Commented] (YARN-1517) AMFilterInitializer with configurable AMIpFilter

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524741#comment-14524741 ] 

Hadoop QA commented on YARN-1517:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12619611/AmFilterInitializer.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7597/console |


This message was automatically generated.

> AMFilterInitializer with configurable AMIpFilter
> ------------------------------------------------
>
>                 Key: YARN-1517
>                 URL: https://issues.apache.org/jira/browse/YARN-1517
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.2.0
>            Reporter: Pramod Immaneni
>            Assignee: Pramod Immaneni
>         Attachments: AmFilterInitializer.patch
>
>
> We need to implement custom logic in a filter for our webservice similar to org.apache.hadoop.yarn.server.webproxy.amfilter.AmIpFilter and it would be convenient if we extended AmIpFilter as the proxy locations already available. 
> We would need to specify a filter initializer for this filter. The initializer would be same as AmFilterInitializer except that it would add our filter instead of AmIpFilter and it would be better if we could reuse AmlFilterInitializer. Can AmFilterInitializer be updated to specify a filter name and filter class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)