Please don’t mess with _version_, that’s used internally for optimistic locking.
I don’t have a clue, really, whether changing the definition will be deleterious
or not.
OTOH, that field was presumably defined by people who put the use of
_version_ in in the first place, so changing it is just ask
So to make things clear, belows what I am expecting
I have a document with a unique id field lets say "uniqueID".
This document has both stored/indexed and not stored/ not indexed fields
Currently I have my pop values in external files but I will instead define
a new field in schema (popVal) which
Let us know how it works. I want to be sure I’m not confusing you
though. There isn’t a “doc ID field”. The structure of an eff file is
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 l
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
Right, but you can use those with function queries. Assuming your eff entry is
a doc ID plus single numeric, I was wondering if you can accomplish what you
need to with function queries...
> On Aug 10, 2020, at 11:30 AM, raj.yadav wrote:
>
> Erick Erickson wrote
>> Ah, ok. That makes sense. I
Erick Erickson wrote
> Ah, ok. That makes sense. I wonder if your use-case would be better
> served, though, by “in place updates”, see:
> https://lucene.apache.org/solr/guide/8_1/updating-parts-of-documents.html
> This has been around in since Solr 6.5…
As per documentation `in place update` is o
Ah, ok. That makes sense. I wonder if your use-case would be better served,
though, by “in place updates”, see:
https://lucene.apache.org/solr/guide/8_1/updating-parts-of-documents.html This
has been around in since Solr 6.5…
Best,
Erick
> On Aug 10, 2020, at 8:24 AM, Akshay Murarka wrote:
>
Hey,
So I have external file fields that have some data that get updated
regularly. Whenever those get updated we need the open searcher operation
to happen. The value in this external files are used in boosting and other
function/range queries.
On Mon, Aug 10, 2020 at 5:08 PM Erick Erickson
wro
In a word, “no”. There is explicit code to _not_ open a new searcher if the
index hasn’t changed because it’s an expensive operation.
Could you explain _why_ you want to open a new searcher even though the index
is unchanged? The reason for the check in the first place is that nothing has
chang
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
10 matches
Mail list logo
