[
https://issues.apache.org/jira/browse/HDFS-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080190#comment-14080190
]
Andrew Wang commented on HDFS-6780:
-----------------------------------
I looked into this a bit. We need something to key the iterator. The simplest
idea is to add the inode ID to EncryptionZone. We could go one step further and
hide it from the end user by having yet-another-EZ-class. We could also
introduce a new EZ-specific ID, which could again be hidden or exposed, and
persisted or not.
Any preference on these approaches? [~cmccabe] [~clamb]? I'm thinking of doing
the hidden inode ID.
> Batch the encryption zones listing API
> --------------------------------------
>
> Key: HDFS-6780
> URL: https://issues.apache.org/jira/browse/HDFS-6780
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: security
> Reporter: Andrew Wang
> Assignee: Andrew Wang
>
> To future-proof the API, it'd be better if the listEZs API returned a
> RemoteIterator.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
