hi,
> Random ≠ unique.
Agree. They are not the same. I don't want a tie breaker, I want to know
how many ties I would face.
The implementation where it's being used has some other (posterior) sorting
criteria. So the question can be rephrased as whether posterior orders have
any effect or not.
You could use the UUIDUpdateProcessorFactory to automatically add a UUID to
each document and use that as the tie-breaker field.
https://solr.apache.org/guide/8_1/update-request-processors.html#uuidupdateprocessorfactory
The chances of collision of UUIDs is well-known, and highly unlikely.
http
Thanks. It's not what I need, but would have it mind.
Sorry, my statement was not clear. I have already replied to Thomas with
further details.
thanks you all
rodolfo
On Tue, Aug 31, 2021, 9:08 AM Andrew Hankinson
wrote:
> You could use the UUIDUpdateProcessorFactory to automatically add a U
I'm trying to upgrade from 8.3.1 to 8.8.1, and we're seeing slower
performance and higher rate of failed requests when testing the upgrade.
The main culprit seems to be when we're burdening the service enough to
start causing "The request took too long to iterate over doc/point values"
warnings. O
Hi,
I have a large solr deployment with solr 7.6.0
128 servers 5 zookeepers on separate systems
each solr host runs 2 solr instances one a primary shard one a secondary shard
port 8080 is always primary aka master replica
port 8090 is always a secondary replica
These are all NRT replicas
so to
We have a solr setup from a very old version (1.4) and we are upgrading it to
8.9. We are stuck at the point that I think the schema.xml is syntactically
free of errors but now giving an error:
Caused by: org.apache.solr.common.SolrException: Could not load conf for core
nwr_col: Can't load sch
Check the attached thread. It might be what you're looking for.
On Tue, Aug 31, 2021 at 4:30 PM Ed Yu wrote:
> We have a solr setup from a very old version (1.4) and we are upgrading it
> to 8.9. We are stuck at the point that I think the schema.xml is
> syntactically free of errors but now givi
Hi,
I suggest you define both id and _root_ fields as string, and you populate
id with uuid generated by UUIDUpdateProcessor in an
updateRequestProcessorChain.
See Solr Wiki - https://cwiki.apache.org/confluence/display/solr/uniquekey
Dominique
Le mar. 31 août 2021 à 22:30, Ed Yu a écrit :