hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10431) Change visibility of KeyStore KeyVersion/Metadata/Options constructor and methods to public
Date Thu, 03 Apr 2014 05:41:15 GMT

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

Alejandro Abdelnur commented on HADOOP-10431:
---------------------------------------------

They need to be public for the KMSKeyProvider (client side), to be able to create them as
return objects when deserializing the response of a HTTP REST API call. Also the KMSServer
need to create a KeyVersion without key material to return back depending on the ACLs the
requestor has.

I can annotate them as private.

Sounds good? 

> Change visibility of KeyStore KeyVersion/Metadata/Options constructor and methods to
public
> -------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10431
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10431
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: HADOOP-10431.patch
>
>
> Making KeyVersion/Metadata/Options constructor and methods public will facilitate {{KeyProvider}}
implementations to use those classes.



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

Mime
View raw message