You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we do not have the ability to do multi-geo points in the same document (meilisearch/product#508), I've been thinking about possibly indexing the same object multiple times using a different _geo for each one and then using a distinctAttribute to to only show a single document (in this case a user with multiple addresses) in the result set.
My question is, is there a recommended approach to doing this with meilisearch-rails or would the better option in this case to completely ignore this gem and just use the native Ruby gem and write our own code around the indexing and querying? It seems a shame to ignore all the additional features that are provided by the rails gem (the search method returning AR objects, pagy integration, etc), but I can't see a natural way to have a single ActiveRecord object index itself in multiple ways.
Any advice would be wonderful.
The text was updated successfully, but these errors were encountered:
There is nothing that I can see intended for this particular use case, though maybe there could be. But first, I would like to know can a user have any number of addresses or are they limited to a fixed number?
I am assuming there are multiple fields in the users table and not a has_many to another table?
Since we do not have the ability to do multi-geo points in the same document (meilisearch/product#508), I've been thinking about possibly indexing the same object multiple times using a different
_geo
for each one and then using adistinctAttribute
to to only show a single document (in this case a user with multiple addresses) in the result set.My question is, is there a recommended approach to doing this with
meilisearch-rails
or would the better option in this case to completely ignore this gem and just use the native Ruby gem and write our own code around the indexing and querying? It seems a shame to ignore all the additional features that are provided by the rails gem (thesearch
method returning AR objects, pagy integration, etc), but I can't see a natural way to have a single ActiveRecord object index itself in multiple ways.Any advice would be wonderful.
The text was updated successfully, but these errors were encountered: