Hi Shawn,
Many thanks for the prompt explanation. You’re right, my email client sent some
weird stuff but as I said I was not concerned with the error per se. We
identified what’s wrong with the delete command (some characters in the query
value used are not valid, like a colon `:`). Here is an unformatted error
message:
org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError:
Cannot parse 'external_id_s:10.1093/acprof:oso/9780198299554.001.0001':
Encountered " ":" ": "" at line 1, column 28.
Given that, we will use double quotes whenever we query string fields in Solr
from now on.
My confusion came from the fact that we even though we use the compositeId
router, it was not capable of knowing where the document was. Now that you
explained how it works, it seems pretty obvious.
Again, many thanks for your time!
From: Shawn Heisey <apa...@elyograg.org.INVALID>
Date: Thursday, 16 November 2023 at 19:01
To: users@solr.apache.org <users@solr.apache.org>
Subject: Re: Solr 8.11.2 - remote updates
*** External email: use caution ***
On 11/16/23 09:38, Saur, Alexandre (ELS-AMS) wrote:
> When I tried to delete a document I noticed this message in the logs:
>
> 16/11/2023, 16:35:04 ERROR x:..._shard3_replica_n59
> ErrorReportingConcurrentUpdateSolrClient Error when calling
> SolrCmdDistributor$Req:
> cmd=delete{_version_=-1782735337591668736,​query=`external_id_s:10.14463/…`,​commitWithin=-1};
> node=ForwardNode: http://10...._shard1_replica_n69/ to
> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.10%2F&data=05%7C01%7Ca.saur%40elsevier.com%7C21c2fce426bc4ad033ac08dbe6ce174f%7C9274ee3f94254109a27f9fb15c10675d%7C0%7C0%7C638357545059525786%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jg57sLlZlvJf0pFkEOVtT0aa0wwInnsV22N5qpUvvYc%3D&reserved=0<http://0.0.0.10/>....
> _shard1_replica_n69/
>
> I’m not interested in the error but rather in what Solr is doing, because the
> CORE information is saying it’s something related to shard 3 (which seems ok,
> since replica 59 is the shard leader for that shard), but the error message
> is saying there was a problem while trying to delete the document from shard
> 1 (in another node)!
> Is this expected?
I am concerned by the presence of backticks in that output surrounding
the query. It might be OK, but seems very odd. There are also other
strange characters in your output, but I do not know how much of that
might be due to your email client or hand-editing. It looks like you
have edited it to remove certain things.
A deleteByQuery would have to be sent to all shards. That's the nature
of the beast. With the compositeId router, a deleteById could be
directed to a specific shard, but not a DBQ.
Thanks,
Shawn
________________________________
Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The
Netherlands, Registration No. 33158992, Registered in The Netherlands.
