[
https://issues.apache.org/jira/browse/DIRECTMEMORY-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572443#comment-13572443
]
Jaromir Hamala commented on DIRECTMEMORY-124:
---------------------------------------------
Hi, iterator.hasNext() currently returns true even if the next object is
expired. So the iterator.next() returns null. Is this desired behaviour?
Iterator probably could retrieve the object in the hasNext() method. And the
next() method should just return it. It the worst case we return an expired
object (but which was not expired during hasNext() call)
> Create an utility class Iterable<V> over Cache<K,V>
> ----------------------------------------------------
>
> Key: DIRECTMEMORY-124
> URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-124
> Project: Apache DirectMemory
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.1-incubating
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Priority: Minor
> Fix For: 0.2
>
>
> That'd be useful to iterate over cache values and at the same time avoid
> loading such items into memory all together.
> E.g. I'm using DM to keep a huge list of graph vertices without spending too
> much memory, but then I need at some point to iterate over them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
