; docid:value
>
> where docid is your . What updating numerics does is allow
> you to update a field in a doc that’s identified by . That
> field is any name you want as long as it’s defined respecting
> the limitations in that link.
>
> Best,
> Erick
>
> > On Aug
use
> your response times to go up is if, up until that point, you’re getting a
> high hit ratio that
> goes down after the cache starts aging out entries. I find this rather
> unlikely, but possible.
>
> Best,
> Erick
>
> > On Aug 13, 2020, at 3:19 AM, Akshay Murarka
Hey Erick,
Thanks for the information about the doc ID field.
So our external file values are single float value fields and we do use
them in functional queries in boost parameter, so based on the definition
the above should work.
So currently we use solr 5.4.0 but are in the process of upgrading
east one doc on each shard is “an exercise for the reader”…
>
> Again, though, perhaps if you explained why you think this is necessary we
> could suggest another approach. At first glance, this looks like an XY
> problem though.
>
> Best,
> Erick
>
> > On Aug 10, 2020,
Hey,
I have a use case where none of the document in my solr index is changing but I
still want to open a new searcher through the curl api.
On executing the below curl command
curl “XXX.XX.XX.XXX:9744/solr/mycollection/update?openSearcher=true&commit=true”
it doesn’t open a new searcher. Below
Hey,
I am using solr-5.4.0 in my production environment and am trying to automate
the reload/restart process of the solr collections based on certain specific
conditions.
I noticed that on solr reload the thread count increases a lot there by
resulting in increased latencies. So I read about r
