, May 25, 2016 9:12 AM
> To: dev@lucene.apache.org
> Subject: Re: Using rows=-1 for "give me all"
>
> On 25/05/16 01:11, Chris Hostetter wrote:
> > : > : Back when we used 4.4.0 I believe a query with rows=-1 returned all
> > : > matching
> >
> &g
On 25/05/16 01:11, Chris Hostetter wrote:
: > : Back when we used 4.4.0 I believe a query with rows=-1 returned all
: > matching
: > Nope -- that's never been how rows=-1 behaved.
: Believe you are wrong. That was how it behaved in 4.4.0
Nope -- not in a regular search it didn't...
OK, thanks.
: > : Back when we used 4.4.0 I believe a query with rows=-1 returned all
: > matching
: > Nope -- that's never been how rows=-1 behaved.
: Believe you are wrong. That was how it behaved in 4.4.0
Nope -- not in a regular search it didn't...
On 23/05/16 23:11, Chris Hostetter wrote:
: Back when we used 4.4.0 I believe a query with rows=-1 returned all matching
: documents. In 5.1.0 (the one we are using now) rows=-1 will trigger a
Nope -- that's never been how rows=-1 behaved.
Believe you are wrong. That was how it behaved in
Hi Steffensen,
Not sure about rows=-1, but retrieval engines are optimized to return top-N
results.
However, there exists special commands for "give me all"
https://cwiki.apache.org/confluence/display/solr/Exporting+Result+Sets
Ahmet
On Monday, May 23, 2016 11:38 PM, Per Steffensen
: Back when we used 4.4.0 I believe a query with rows=-1 returned all matching
: documents. In 5.1.0 (the one we are using now) rows=-1 will trigger a
Nope -- that's never been how rows=-1 behaved.
The fact that it didn't return an error is some older versions of solr
(and may have behaved
Hi
Back when we used 4.4.0 I believe a query with rows=-1 returned all
matching documents. In 5.1.0 (the one we are using now) rows=-1 will
trigger a validation exception. If I remove the code that throws that
exception, it seems like rows=-1 behaves like rows=0. Has the support
for rows=-1
