hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoy Antony (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10221) Add a plugin to specify SaslProperties for RPC protocol based on connection properties
Date Mon, 10 Mar 2014 19:46:45 GMT

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

Benoy Antony updated HADOOP-10221:
----------------------------------

    Attachment: HADOOP-10221.patch

Attaching the patch which fixes the problems reported by [~daryn].

The RefelctionUtils newInstance calls the constructor  first and then calls setConf on the
constructed object. I can initialize a field based on configuration in setConf. But I cannot
make it a final field since a final field can be initialized only inside a constructor. So
I cannot take advantage of the thread safety offered by the final field when using newInstance.

That's why I added constructInstance which accepts the configuration object and passes it
to the constructor of the object being created.




> Add a plugin to specify SaslProperties for RPC protocol based on connection properties
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10221
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10221
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.2.0
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>         Attachments: HADOOP-10221.no-static.example, HADOOP-10221.patch, HADOOP-10221.patch,
HADOOP-10221.patch, HADOOP-10221.patch, HADOOP-10221.patch, HADOOP-10221.patch, HADOOP-10221.patch,
HADOOP-10221.patch, HADOOP-10221.patch
>
>
> Add a plugin to specify SaslProperties for RPC protocol based on connection properties.
> HADOOP-10211 enables client and server to specify and support multiple QOP.  Some connections
needs to be restricted to a specific set of QOP based on connection properties.
> Eg. connections from client from a specific subnet needs to be encrypted (QOP=privacy)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message