PHANTOM
🇮🇳 IN
Skip to content

Do not exclude explicitly null fields when sorting#6136

Open
chrisbenincasa wants to merge 1 commit intomeilisearch:mainfrom
chrisbenincasa:sort-undefined-cols
Open

Do not exclude explicitly null fields when sorting#6136
chrisbenincasa wants to merge 1 commit intomeilisearch:mainfrom
chrisbenincasa:sort-undefined-cols

Conversation

@chrisbenincasa
Copy link

@chrisbenincasa chrisbenincasa commented Jan 30, 2026

Related issue

None yet - something I noticed in my project that deployed a local Meilisearch on user's machines: https://github.com/chrisbenincasa/tunarr

Happy to open one to discuss further if necessary

Requirements

⚠️ Ensure the following requirements before merging ⚠️

  • Automated tests have been added.
  • If some tests cannot be automated, manual rigorous tests should be applied.
  • ⚠️ If there is any change in the DB:
    • Test that any impacted DB still works as expected after using --experimental-dumpless-upgrade on a DB created with the last released Meilisearch This seemed to work for me but I can perform something more official if necessary
    • Test that during the upgrade, search is still available (artificially make the upgrade longer if needed)
    • Set the db change label.
  • If necessary, the feature have been tested in the Cloud production environment (with prototypes) and the Cloud UI is ready. Don't know know to do this
  • If necessary, the documentation related to the implemented feature in the PR is ready.
  • If necessary, the integrations related to the implemented feature in the PR are ready.

Open Questions

  • Is there an implication that I may not be aware off to adding these null fields to the sortable index if necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant