[
https://issues.apache.org/jira/browse/HDFS-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086343#comment-16086343
]
Chen Liang commented on HDFS-12083:
-----------------------------------
Thanks [~nandakumar131] for updating the patch! It seems to me range get
becomes a bit tricky when the "previous key" is something unknown. For example
say I just want to extract N keys starting from some key K. With this change,
does it mean I will have to call get key K first, followed by a separate
getRangeKV call to get the rest N-1 keys? how about passing a new boolean flag
to indicate whether including start key or not? I have no strong opinion on
this, either way is fine to me, just a thought.
> Ozone: KSM: previous key has to be excluded from result in listVolumes,
> listBuckets and listKeys
> ------------------------------------------------------------------------------------------------
>
> Key: HDFS-12083
> URL: https://issues.apache.org/jira/browse/HDFS-12083
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Nandakumar
> Assignee: Nandakumar
> Priority: Critical
> Attachments: HDFS-12083-HDFS-7240.000.patch,
> HDFS-12083-HDFS-7240.001.patch
>
>
> When previous key is set as part of list calls [listVolume, listBuckets &
> listKeys], the result includes previous key, there is no need to have this in
> the result.
> Since previous key is present as part of result, we will never receive an
> empty list in the subsequent list calls, this makes it difficult to have a
> exit criteria where we want to get all the values using multiple list calls
> (with previous-key set).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
