Yes, id is unique key.
> I bet that if you redefined your updateHandler to give it some name other
than “/update” in solrconfig.xml two things would happen:
Hmm, nice. I didn't think of that but that would definitely identify the
problem. We do have other scripts writing to the index but they ar
Is your “id” field is your , and is it tokenized? It shouldn’t be,
use something like “string” or keywordTokenizer. Definitely do NOT use, say,
text_general.
It’s very unlikely that records are not being flushed on commit, I’m 99.99%
certain that’s a red herring and that this is a problem in y
Thanks Eric. My knowledge is fairly limited but 1) sounds feasible. Some
logs:
I write a bunch of recods to Solr:
2020-09-28 11:01:01.255 INFO (qtp918312414-21) [ x:vnc]
o.a.s.u.p.LogUpdateProcessorFactory [vnc] webapp=/solr path=/update
params={json.nl=flat&omitHeader=false&wt=json}{add=[
ta
There are several possibilities:
1> you simply have some process incorrectly updating documents.
2> you’ve changed your schema sometime without completely deleting your old
index and re-indexing all documents from scratch. I recommend in fact indexing
into a new collection and using collection
