AkkomaGang/akkoma
AkkomaGang/akkoma
17
68
Fork 110
Code Issues 145 Pull requests 16 Projects 2 Releases 21 Packages Wiki Activity

Make search result order match the order of objects received from Meilisearch #579

Closed
AdamK2003 wants to merge 1 commit from AdamK2003/akkoma:meilisearch-result-order into develop
pull from: AdamK2003/akkoma:meilisearch-result-order
merge into: AkkomaGang:develop
Conversation 1 Commits 1 Files changed 1 +7 -2
AdamK2003 commented 2023-07-04 10:04:40 +00:00
First-time contributor
Copy link

The search results are normally sorted by published date before getting to the client, which makes the result order not match the Meilisearch result order if you tweak your Meilisearch ranking settings. This PR sorts the results back into the initial Meilisearch order after fetching them from the repo.

The search results are normally sorted by published date before getting to the client, which makes the result order not match the Meilisearch result order if you tweak your Meilisearch ranking settings. This PR sorts the results back into the initial Meilisearch order after fetching them from the repo.
Fix search result order for Meilisearch
Some checks are pending
ci/woodpecker/pr/woodpecker Pipeline is pending
Details
ci/woodpecker/pull_request_closed/woodpecker Pipeline was successful
Details
7dd439807f
Oneric commented 2024-05-04 00:04:38 +00:00
Owner
Copy link

@AdamK2003 can you test whether Oneric/akkoma@f32335742d also works for you? It directly fetches results in the correct order instead of using a O(n²) resort afterwards, but i don’t have Meilisearch set up.

EDIT: i was now able to confirm this works myself, see #772

@AdamK2003 can you test whether https://akkoma.dev/Oneric/akkoma/commit/f32335742daf8b037b136584f859cb59666edf65 also works for you? It directly fetches results in the correct order instead of using a O(n²) resort afterwards, but i don’t have Meilisearch set up. **EDIT:** i was now able to confirm this works myself, see #772
Oneric closed this pull request 2025-05-05 19:26:17 +00:00
Some checks are pending
ci/woodpecker/pr/woodpecker Pipeline is pending
Details
ci/woodpecker/pull_request_closed/woodpecker Pipeline was successful
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
approved, awaiting change

   
bug

Something is not working

  
cannot reproduce

   
configuration

This requires config changes

  
documentation

This is about human-readable docs

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
extremely low priority

   
feature request

Something new?

  
Fix it yourself

Support has been attempted

  
help wanted

Need some help

  
invalid

Something is wrong

  
mastodon_api

   
needs change/feedback

Issue or PR is stalled on response from the author or a third party

  
needs docs

   
needs tests

   
not a bug

   
not our bug

Bug in a dependency of ours (meaning we can't just fix it), or in another AP implementation or client interfacing with Akkoma (which needs to be fixed on their end)

  
planned

   
pleroma_api

   
privacy

   
question

More information is needed

  
static_fe

   
triage

   
wontfix

This won't be fixed

No labels
approved, awaiting change
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AkkomaGang/akkoma!579
No description provided.