[
https://issues.apache.org/jira/browse/HADOOP-10430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973068#comment-13973068
]
Owen O'Malley commented on HADOOP-10430:
----------------------------------------
Actually, after thinking about it a bit more, I see your point. I like Andrew's
point about having a cursor, but I'd rather keep the interface simpler. How
about letting the caller control the windowing by providing a list of names:
{code}
List<Metadata> getMetadata(String... names);
{code}
The CLI could then get the list of names and break it into 1000 name chunks.
Thoughts?
> KeyProvider Metadata should have an optional description, there should be a
> method to retrieve the metadata from all keys
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10430
> URL: https://issues.apache.org/jira/browse/HADOOP-10430
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 3.0.0
>
> Attachments: HADOOP-10430.patch, HADOOP-10430.patch,
> HADOOP-10430.patch, HADOOP-10430.patch
>
>
> Being able to attach an optional description (and show it when displaying
> metadata) will enable giving some context on the keys.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
