[
https://issues.apache.org/jira/browse/HADOOP-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963129#comment-13963129
]
Larry McCay commented on HADOOP-10431:
--------------------------------------
I am generally uncomfortable opening up the internals of the API so that they
can be directly used in the contract of another API for the server. As I see it
there are a couple drawbacks to that:
1. exposing more of the implementation publicly means that they will be used
directly and harder to change later
2. changing them may have implications on the server API contract that would
also make changing them trickier
Of course, there is the benefit of code reuse but I feel like that reuse would
potentially paint us into a corner more than benefit either API.
What would the alternative of having a separate databinding object graph look
like for the server?
> 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)
