I set up this small Gist to demonstrate a possible bug in Solr's Re-ranking / LTR / QueryComponent.
When combining Re-Ranking and Sorting in a query in a Solr Cloud environment on a collection with multiple shards, the result is sorted randomly.
# writes additional node_aws_info metrics to node exporter | |
* * * * * node-exporter /usr/local/bin/node-exporter-instance-info.sh |
name: terraform state drift detection | |
# Execute this action on push to main and everyday at 7am | |
on: | |
push: | |
branches: | |
- main | |
workflow_dispatch: | |
schedule: | |
- cron: '0 7 * * *' |
I set up this small Gist to demonstrate a possible bug in Solr's Re-ranking / LTR / QueryComponent.
When combining Re-Ranking and Sorting in a query in a Solr Cloud environment on a collection with multiple shards, the result is sorted randomly.
I set up this small Gist to help demonstrate an edge case when running Solr as a TLOG/PULL replica ensemble with authentication enabled and authorization being rather strict.
The problem is that in said environment, the PULL replica cannot check the TLOG leader
replicas for updates. It get's rejected with a 401
HTTP error code.
{"lastUpload":"2021-05-31T11:41:23.468Z","extensionVersion":"v3.4.3"} |
# download | |
wget http://repo.or.cz/w/wortliste.git/blob_plain/master:/wortliste | |
# easy things | |
awk -F ';' '{print $1;}' > list_words_dictionary.de.txt | |
# ok, complex | |
grep -v ";-2-;" wortliste |awk -F ';' '{print $2;}' | tr -d "[·|-<>]" | grep "=" | awk -F '=' '{print $1"\n"$2"\n"$3"\n"$4;}' | sort -u | tr [:upper:] [:lower:] >> list_words_dictionary.de.txt | |
# reset |
varnishd -C -f /etc/varnish/main.vcl |
80470 => 80470 | |
ABC => ABC | |
ABM => ABM | |
ACL => ACL | |
ACPI => ACPI | |
ADAC => ADAC | |
ADSL => ADSL | |
AEG => AEG | |
AG => AG |