Avoid algolia index number limitation in dev

[arkid15r]

Is your feature request related to a problem? Please describe.
We're facing algolia index limit (20 instances) problem. For development environment we want to control what exactly is indexed

Describe the solution you'd like
Implement enable/disable index functionality for dev environment.
Add a custom register decorator to apps.common.index that behaves like original algoliasearch_django.decorators.register decorator for enabled index models and does nothing for models we don't want to index locally. It should skip indexing for local (development) environment only. Make sure a model is identified by app/model name pair to avoid confusion if same name models exist in different apps.
Create a list of excluded models (all other models are indexed by default). Make sure there is a way to override the list using .env variable (a list of comma separated values with app/models name items to override).

[bhagyashree980]

Please assign me

[bhagyashree980]

I will find out the solution

[arkid15r]

@bhagyashree980 this is an advanced task that requires Algolia knowledge and Nest backend experience. I was hoping @nitinawari could tackle that.

[nitinawari]

Ok assign plz

[nitinawari]

I have analyzed the indices in Algolia and identified
8 indices used for sorting
and
5 indices for search suggestions.
If any contributor needs to work on sorting or search suggestions, they can easily enable these indices by updating the .env file.

[arkid15r]

I have analyzed the indices in Algolia and identified 8 indices used for sorting and 5 indices for search suggestions. If any contributor needs to work on sorting or search suggestions, they can easily enable these indices by updating the .env file.

Sounds fair, we're on the same page.

[arkid15r]

Any updates on this? It's something we want to address rather sooner than later.

[nitinawari]

i really sorry for late update , now PR is open for review