edismas is quite different from straight Lucene.
Try attaching &debug=query to the input and
you’ll see the difference.
Best,
Erick
> On May 30, 2020, at 12:32 AM, gnandre wrote:
>
> Hi,
>
> I have following query which works fine as a lucene query:
> +(topics:132)^0.02607211 (topics:146)^0.0
Thanks again, Erick, for pointing us in the right direction.
Yes, I am seeing heavy disk I/O while querying. I queried a single
collection. A query for 10 rows can cause 100-150 MB disk read on each
node. While querying for a 1000 rows, disk read is in range of 2-7 GB per
node.
Is this normal? I
Best guess is that your indexes are too big for your memory.
I think your focus on number of rows is misleading you, you’ll
see why in a moment.
Lucene indexes are essentially accessed randomly, there’s
very little locality. Here’s an excellent article explaining
how Lucene uses memory:
https://b
I think this question here in this thread is similar to my question.
https://lucene.472066.n3.nabble.com/Lucene-Query-to-Solr-query-td493751.html
As suggested in that thread, I do not want to use toString method for
Lucene query to pass it to the q param in SolrQuery.
I am looking for a function
