Limitations of scout search with active filters or via other resources

[sanderbaas]

We are struggling to enable scout search on our resources because of two limitations.

1. Scout search does not work well with filters because the filters are applied after the actual Scout search is done. Also Scout search returns a limited number of results (max 1000).
   So when I have a resource with 500K records, the change is big that the 1000 ID's returned by scout search do not meet the conditions of the active filters.

I can solve this by adding filterableAttributes to index-settings in config/scout.php for each filter, reindex, and adding where clauses of all active filters to the scoutQuery of the resource.

2. Searching in resources that are loaded via other resources produces search results not limited to the viaResourceId.

So when we have an Order resource that is available as a HasMany relationship on a Customer resource, searching a specific order from a Customer resource will be done in all Customer records, not only the related Customer resource. This can be solved by adding filterableAttributes to index-settings in config/scout.php and adding a where clause to the scoutQuery of the resource.

Adding the where clauses manually to the scoutQuery of resources means a lot of work each time a filter is added or when a relationship changes.

Are these limitations known limitations or am I seeing it wrong? Because I would love to use scout to speed up the searches in our system.

We are using Meilisearch 1.0.1 by the way.