[
https://issues.apache.org/jira/browse/HDFS-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-8677:
--------------------------------
Attachment: HDFS-8677-HDFS-7240.04.patch
Thanks, the intended behavior is just as you described. v04 patch updates
Javadocs on seek and nextKey to make it explicit.
{code}
+ * If the key exists then a subsequent {@link #nextKey()} call
+ * must return the same key.
*
* @throws IOException if the operation failed for any reason.
*/
@@ -72,7 +74,9 @@
void next();
/**
- * Retrieve the next key in the container.
+ * Retrieve the key at the iterator position.
+ * Retrieve the next key in lexical order if the iterator was positioned
+ * at a non-existent key via {@link #seek(byte[])}.
{code}
> Ozone: Introduce KeyValueContainerDatasetSpi
> --------------------------------------------
>
> Key: HDFS-8677
> URL: https://issues.apache.org/jira/browse/HDFS-8677
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HDFS-8677-HDFS-7240.01.patch,
> HDFS-8677-HDFS-7240.02.patch, HDFS-8677-HDFS-7240.03.patch,
> HDFS-8677-HDFS-7240.04.patch
>
>
> KeyValueContainerDatasetSpi will be a new interface for Ozone containers,
> just as FsDatasetSpi is an interface for manipulating HDFS block files.
> The interface will have support for both key-value containers for storing
> Ozone metadata and blobs for storing user data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
