[
https://issues.apache.org/jira/browse/MAVIBOT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822297#comment-13822297
]
Emmanuel Lecharny commented on MAVIBOT-21:
------------------------------------------
IMO, those methods are not the best possible implementation. In order to get
the next or previous key, one has to do :
cursor.moveToNextNonDuplicateKey();
followed by
Tuple<Long, String> tuple = cursor.next();
It would be way easier to have :
Tuple<Long, String> tuple = cursor.nextNonDuplicateKey()
The pb is that the positioning of the cursor s way to complex in the first
case, and the semantic is weird : why should we do a next() instead of a prev()
? Aren't we supposed to be positioned already ?
> Navigation with the moveToNextNonDuplicateKey/moveToPrevNonDuplicateKey is
> broken
> ---------------------------------------------------------------------------------
>
> Key: MAVIBOT-21
> URL: https://issues.apache.org/jira/browse/MAVIBOT-21
> Project: Mavibot
> Issue Type: Bug
> Affects Versions: 1.0.0-M2
> Reporter: Emmanuel Lecharny
> Assignee: Emmanuel Lecharny
> Fix For: 1.0.0-M3
>
>
> Due to the changes in the way we navigate in the tree, those two methods are
> now broken.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
