[
https://issues.apache.org/jira/browse/YARN-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853103#comment-13853103
]
Hadoop QA commented on YARN-1517:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12619611/AmFilterInitializer.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/2703//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2703//console
This message is 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.1.4#6159)
