On 9/22/2020 10:22 PM, Anuj Bhargava wrote:
How to solve this issue? How to replace it?
SolrResourceLoader
Solr loaded a deprecated plugin/analysis class [solr.DataImportHandler].
Please consult documentation how to replace it accordingly.
That is a generic message about using deprecated featu
How to solve this issue? How to replace it?
SolrResourceLoader
Solr loaded a deprecated plugin/analysis class [solr.DataImportHandler].
Please consult documentation how to replace it accordingly.
In 6.3, q.op param used to affect q as well fq param behavior. E.g. if q.op
is set to AND and fq is set to id:(1 2 3), no results will show up but if
it is set to OR then all 3 results will show up. This does not happen in
Solr 8.5.2 anymore.
Is this a bug? What does one need to do in Solr 8.5.2 t
TimeAllowed stops looking when the timer expires. If it hasn’t found any docs
with a
non-zero score by then, you’ll get zero hits.
It has to be this way, because Solr doesn’t know whether a doc is a hit until
Solr scores it.
So this is normal behavior, assuming that some part of the processing
I have timeAllowed=2000 (2sec) and having mostly 0 hits coming out. Should
I have more than 0 results?
Jae
Thanks, Erick. I should probably keep a tally of how many beers I owe
you ;-)
On 21/09/2020 14:50, Erick Erickson wrote:
> In a word, yes. G1GC still has spikes, and the larger the heap the more
> likely you’ll be to encounter them. So having multiple JVMS rather than one
> large JVM with a gin
This is solved by using local parameters. So
{!func}sub(num_tokens_int,query({!dismax qf=field_name v=${text}}))
works
On Mon, Sep 21, 2020 at 7:43 PM krishan goyal wrote:
> Hi,
>
> I have use cases of features which require a query function and some more
> math on top of the result of the qu
