I may have got this wrong, but I think it might be better to shard
randomly, not on a value from one of your source documents, as otherwise
certain searches will only hit some of the shards and possibly overload
them. This might also be the cause of the behaviour below.
Charlie
On 30/11/2023
I thought multi valued field was not supported as routing field?
You'll likely need to choose a single-valued stable property for routing and
not a value that a field that a single document can have several different
values for.
So have a look at your schema for other candidate single-valued ro
Hi,
I have a schema with a UUID field type configured as a unique key.
I recently upgraded my Solr installation to 9.3 (from 7.6) and my application
stopped working. It turns out that Solr has stopped encoding UUIDs as strings
in the JSON response writer.
Whereas before I would get:
"id"
On 11/26/23 03:40, Andrew Hankinson wrote:
I recently upgraded my Solr installation to 9.3 (from 7.6) and my application
stopped working. It turns out that Solr has stopped encoding UUIDs as strings
in the JSON response writer.
Whereas before I would get:
"id":"76af09e3-db43-4e7e-a46f-9bf03e
It might have the same root cause like
https://issues.apache.org/jira/browse/SOLR-10653?filter=-3 Could you share
more details about your env setup: is it "SolrCloud"? is it /get or /select
? etc.
On Fri, Dec 1, 2023 at 12:05 AM Andrew Hankinson
wrote:
> Hi,
>
> I have a schema with a UUID field
No SolrCloud, complete wipe and reindex of the data, select handler.
> On 1 Dec 2023, at 07:54, Mikhail Khludnev wrote:
>
> It might have the same root cause like
> https://issues.apache.org/jira/browse/SOLR-10653?filter=-3 Could you share
> more details about your env setup: is it "SolrCloud"?
