Preserve Meilisearch’s result ranking #772
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#772
Loading…
Reference in a new issue
No description provided.
Delete branch "Oneric/akkoma:search-meili-order"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Supersedes #579
Meilisearch was easier to setup than initially presumed so i was now able to test this myself. Previously top results were reorderd by date, now Meilisearch’s ranking is respected; note how reordering pushed the top Meilisearch result down to the end of the list:
Compared to #579 this avoids a costly O(n²) resort in Elixir by just retrieving objects in the right order to begin with.
Side note: Meilisearch’s ranking for this particular query almost matches what
ORDER BY ts_rank_cd(vector, query, 16)
would yield if it was used in the default GIN search.@ -59,2 +59,3 @@
You will see a "Default Admin API Key", this is the key you actually put into your configuration file.
Depending on your Meilisearch version, you will either see a "Default Admin API Key" or some line starting with "Use it for anything that is not a search operation. Caution! Do not expose it on a public frontend:".
This is the key you actually put into your configuration file.
Wondering if it would make more sense to limit the admin API key to just admin tasks and use a separate key for just searches done via our APIs..
repusehd, using separate search and admin keys is now possible and instead of changing documentation to match the output of our
show-keys
task,show-keys
is changed to display Meilisearch'sname
parameter if present instead ofdescription
.560c5a4b5d
toe38fa81518
e38fa81518
todba848032c
dba848032c
to17f49efb97
PR looks ok, fails lint though
although this is notably lacking a test - can you add one?
get_presorted_create_by_object_ap_id/1
seems a good one to test to check the main component of this works17f49efb97
tofc7e07f424
oops, forgot to rerun lint after adding
search_key
Fixed now and test added
all good now, thanks!