hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6337) Update FilterInitializer class to be more visible and take a conf for further development
Date Tue, 27 Oct 2009 23:50:59 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jakob Homan updated HADOOP-6337:

    Attachment: HADOOP-6337.patch

Patch with changes:
* Update FilterInitializer class
* Update test cases that test FilterInitializer
* Update where filters are initialized in http server.

No new tests as very difficult to test these changes.  Manually verified that can now create
a FilterInitializer in another package and that the new param is seen.

> Update FilterInitializer class to be more visible and take a conf for further development
> -----------------------------------------------------------------------------------------
>                 Key: HADOOP-6337
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6337
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.22.0
>         Attachments: HADOOP-6337.patch
> Currently the FilterInitializer class, used to filter access to the Hadoop web interfaces,
has its main method, initFilter, set to package private.  This means that any classes wishing
to implement this type must be in the same package.  This should be public so FilterInitializers
can reside in other packages.  
> Also, currently all parameters to the FilterInitializer must be provided at compile time
(or via a different configuration method).  It would be better if the FilterInitalizer::initFilter
received a Configuration parameter so it can pull conf values out at run-time.  Alternatively,
the class could implement Configured, but that seems heavier than is needed at this point.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message