Yes, I see it now, thank you!
We have migrated form Jackrabbit 1.x to Jackrabbit 2.x and found this
out. We use queries not to only perform fulltext searches, aka Google,
where it is not mandatory to know the exact count of results. That is
why I am searching now for a (good performing) way to
On Thu, Feb 18, 2010 at 15:33, Sergiy Shyrkov
wrote:
> Thank you, Guo!
> I should have searched in dev list also.
Note that it this is explicitly mentioned also right in the javadocs
of getSize(), for both JCR 1.0 and 2.0:
http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/RangeIterator.
Thank you, Guo!
I should have searched in dev list also.
Kind regards
Sergiy
On 18.02.2010 15:18, Guo Du wrote:
On Thu, Feb 18, 2010 at 2:12 PM, Sergiy Shyrkov
wrote:
I always get -1 as the size of an non-empty iterator (I can perfectly
iterate over it and get nodes).
The -1 discu
On Thu, Feb 18, 2010 at 2:12 PM, Sergiy Shyrkov
wrote:
> I always get -1 as the size of an non-empty iterator (I can perfectly
> iterate over it and get nodes).
The -1 discussed recently:
http://jackrabbit.markmail.org/message/7jzk7d6e7raimpxk?q=Queries+not+working+in+Jackrabbit+2.0
-Guo
Hello,
I recently noticed strange behaviour with the size of query results
(using Jackrabbit 2.0.0).
In the following example:
Query query = ...;
NodeIterator ni = query.execute().getNodes()
if (ni.hasNext()) {
long count = ni.getSize();
...
}
I always get -1 as the size of an non-empty
