[
https://issues.jboss.org/browse/ISPN-2352?page=com.atlassian.jira.plugin....
]
Marko Lukša commented on ISPN-2352:
-----------------------------------
If I remember correctly, this bug was just something I noticed when I was changing the
Query result iterators in Infinispan. So I don't actually have anything in CapeDwarf
that would be affected by this (we always create a fresh query instance - we never call
iterator() twice on the same instance).
Second invocation of ClusteredQueryImpl.lazyIterator() yields results
in reverse order
--------------------------------------------------------------------------------------
Key: ISPN-2352
URL:
https://issues.jboss.org/browse/ISPN-2352
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 5.1.8.Final, 5.2.0.Alpha4
Reporter: Marko Lukša
Assignee: Galder Zamarreño
Priority: Minor
Fix For: 5.2.0.Beta6, 5.2.0.Final
When you invoke lazyIterator() for the 2nd time on the same ClusteredQueryImpl instance,
the iterator returns results in reverse order. This only occurs when the query has a Sort
specified.
Caused by DistributedIterator.setTopDocs(), which inverts the reverse flag on SortField.
The same is probably also true for ClusteredQueryImpl.iterator()
--
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