Hi Mike,
can you please elaborate?
Where can I find the test?
TIA
Michael McCandless-2 wrote:
>
> Yes, I believe so (we have a unit test asserting this).
>
> But, there's no guarantee of cross-version compatibility of the serialized
> form.
>
> Mike
>
--
View this message in context:
h
We're holding a free webinar about relevancy enhancements in our
commercial version of Solr. Details below.
-Yonik
http://www.lucidimagination.com
-
Join us for a free technical webcast
"Better Search Results Faster with Apa
And I kind of skipped over the query part. Between the two of us, we
might make one decent code reviewer :D
Erick
On Wed, Dec 8, 2010 at 8:46 AM, Simon Willnauer <
simon.willna...@googlemail.com> wrote:
> On Wed, Dec 8, 2010 at 2:43 PM, Erick Erickson
> wrote:
> > I don't think this code is doi
On Wed, Dec 8, 2010 at 2:43 PM, Erick Erickson wrote:
> I don't think this code is doing anything predictable. From the javadocs for
> TermDocs.skipTo():
> Skips entries to the first beyond the current whose document number is
> greater than or equal to *target*.
>
> Returns true iff there is such
Hey there,
so let me quickly explain what is going on here.
you search for: sql server (without quotes) which QueryParser will
turn into a BooleanQuery like sql OR server since the StandardAnalyzer
you are using splits on whitespaces. That query will return all
document either containing sql or s
I don't think this code is doing anything predictable. From the javadocs for
TermDocs.skipTo():
Skips entries to the first beyond the current whose document number is
greater than or equal to *target*.
Returns true iff there is such an entry.
You're not testing the return value from skipTo. The do
Setting it to a high value shouldn't have any noticeable effect on the
normal queries. And since your high values aren't very high I'd
expect them to be fine too. Try it and see.
btw 2.4.0 is ancient.
--
Ian.
On Wed, Dec 8, 2010 at 7:05 AM, Raghavendra D.V Rao (rarao2)
wrote:
> Update on my
Update on my previous query.
In our application environment, our queries will typically contain
200-300 clauses. The chances of clauses becoming 5000 is less.
Hence we are interested in knowing the actual impact of setting the
setMaxClauseCount () to high value on the normal queries, cont
Hi,
Thanks for your replay!!!
Below is code I am using for search
String line="sql server";
IndexReader reader = IndexReader.open(FSDirectory.open(new File(indexpath)),
true); // contains index file p
Hi All,
We have a requirement where in we need to construct a BooleanQuery, with
the TermQueries, whose count is large , but that it is somewhat fixed
number. It could be around a 5000 or 6000.
At present we are hitting the BooleanQuery.TooManyClauses exception, as
the default count of ma
10 matches
Mail list logo
