This repository has been archived by the owner on Mar 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
Search API — Filters - Introduce IN and EXISTS and describe filter capabilities in more precisely #163
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EXISTS IN NOT (new behaviour) != (new behaviour)
3 tasks
gmourier
added
Ready For Review
Feature specification must be reviewed.
and removed
Ready For Review
Feature specification must be reviewed.
labels
Aug 2, 2022
gmourier
changed the title
Write a specification for the new (and old) search filters
Filters - Dedicated specification (catch-up) and introduce IN and EXISTS
Aug 2, 2022
gmourier
changed the title
Filters - Dedicated specification (catch-up) and introduce IN and EXISTS
Filters - Introduce IN and EXISTS and describe filter capabilities in more precisely
Aug 9, 2022
gmourier
reviewed
Aug 9, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is super clear @loiclec! Thanks
irevoire
suggested changes
Aug 10, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, you documented so many edge cases!
|
||
Note that `attribute != value` is equivalent to `NOT attribute = value`. | ||
|
||
Furthermore, there is no way to write a filter to select documents which contain a value that is different than a given string or number. In the example above, `size != 1` did not select the document with id `1`, even though its `size` attribute contains the value `"L"`, which is different than `1`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice I never thought of that
gmourier
changed the title
Filters - Introduce IN and EXISTS and describe filter capabilities in more precisely
Search API — Filters - Introduce IN and EXISTS and describe filter capabilities in more precisely
Aug 24, 2022
Co-authored-by: Tamo <tamo@meilisearch.com> Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
irevoire
approved these changes
Oct 3, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
gmourier
approved these changes
Oct 3, 2022
Thank you @loiclec ! |
gmourier
added
Implemented
Feature specification has been implemented.
and removed
Ready For Review
Feature specification must be reviewed.
labels
Oct 3, 2022
gmourier
added a commit
that referenced
this pull request
Oct 3, 2022
…pabilities in more precisely (#163) * Write a specification for the new (and old) search filters EXISTS IN NOT (new behaviour) != (new behaviour) * Apply suggestions from code review Co-authored-by: Tamo <tamo@meilisearch.com> Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com> Co-authored-by: Tamo <tamo@meilisearch.com> Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com>
gmourier
added a commit
that referenced
this pull request
Oct 3, 2022
* Bump openapi spec version to v0.29 * Update 0001-script-based-tokenizer.md (#159) Change tokenizer specs to better fit Charabia implementation * Update the geosearch error (#161) Implemented in meilisearch/milli#561 * Auto-batching - Enable feature by default and remove unwanted options (#162) * Update specs according to new auto-batching behavior * update batchUid to make it internal and hidden from a task resource representation * Remove the batchUid mentions from the task API * Update open-api.yaml Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com> * update future possibilities Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com> * Search API — Filters - Introduce IN and EXISTS and describe filter capabilities in more precisely (#163) * Write a specification for the new (and old) search filters EXISTS IN NOT (new behaviour) != (new behaviour) * Apply suggestions from code review Co-authored-by: Tamo <tamo@meilisearch.com> Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com> Co-authored-by: Tamo <tamo@meilisearch.com> Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com> * Add missing settings object in the task details field of a settingsUpdate task type (#164) * Remove `name` from indexes resource definition (#165) * Misc — Soft deleted documents (Performance optimization) (#168) * create a spec for the soft deleted documents * Rename spec file, minor adjustements * Replace You and We by A user and Meilisearch Co-authored-by: Guillaume Mourier <guillaume@meilisearch.com> * Add Stats Seen event (#169) * Add examples component for each summarized task type (#170) * Version API — Catch up (#171) * Add version-api.md * Add PR number as a spec file prefix * Add health-api.md (#172) * Search API — Add `matchingStrategy` parameter with `last` / `all` strategies (#173) * Introduce a proposal to boot the specification * Update telemetry * Replace wordMatchingStrategy by matchingStrategy * fix missing backtick md Co-authored-by: Many the fish <legendre.maxime.isn@gmail.com> Co-authored-by: Tamo <tamo@meilisearch.com> Co-authored-by: Clémentine Urquizar - curqui <clementine@meilisearch.com> Co-authored-by: Loïc Lecrenier <loic.lecrenier@me.com> Co-authored-by: cvermand <33010418+bidoubiwa@users.noreply.github.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
With the release of Meilisearch v0.29.0, we hope to add more filter operators and to change the behaviour of
NOT
and!=
. This PR updates the specification so that it is up-to-date with these changes. I have also updated it to be more precise and complete.Changes
search-api.md
Out Of Scope
N/A
Attention To Reviewers
I am not entirely sure what the expected style of the spec is supposed to be, so please let me know if something can be slightly improved or if it is completely wrong :)
Misc
N/A