-
|
Hi, would it be possible to make all attributes filterable just like you can with searchable attributes? Right now what happens if I update the filterable attributes with I'd like to do this instead of going through the documents in the database to find all distinct attributes |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Hey, @eikooc, you're right. Meilisearch doesn't currently support this. In the meantime, the only trick I can give you is that the nested fields already support this feature. {
"filterable": {
"id": 38,
"price": 85,
"colors": ["red", "green"]
}
// You can put any non-filterable fields you want here
}Then you can make the Warning But take care. Making everything filterable, including the fields that should be searchable, is generally not a good idea. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, thank you for the workaround. Regarding your
And I still want to be able to search for movies based on their title in other queries? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, The filter is going to match exactly your title, so In this case, I still think it doesn't make sense to make the In summary, your settings would be: { "filterableAttribute": ["genre", "rating"], "searchableAttribute": ["title"] }And your query: { "filter": "genre in [romance, action] AND rating > 7.5", "q": "My little query -batman" } |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, that helps my understanding a bit. But it would still be great not having to do the workaround for other use-cases. E.g. having user defined fields be filterable, so every time they add new fields to let's say the movies index (they figure out a "producers" field would be nice). They could add that and it would automatically be filterable |
Beta Was this translation helpful? Give feedback.
Hey, @eikooc, you're right. Meilisearch doesn't currently support this.
In the meantime, the only trick I can give you is that the nested fields already support this feature.
If you put all your filterable fields in a sub-object like that:
Then you can make the
filterablefield, well, filterable:{ "filterableAttributes": ["filterable"] }, and it should make all the fields inside it filterable.Warning
But take care. Making everything filterable, including the fields that should be searchable, is generally not a good idea.
You want to have as few…