I’ve been suffering an issue with a growing collection that happens to store filter-related data in a way which may not be the most optimal one: all possible filter combinations in a list (country, city, …, actually all filters are dynamic - not only in value but in key, you could introduce a new filter anytime you want).
This causes a quite high cardinality, making collections not usable since you can’t really retrieve more than 2 weeks of data.
My question here is… How do you react to this kind of explossion in MongoDB? Which is the most optimal way to store dynamic filters in here (I can imagine they can’t be attributes of the document by themselves? How bad is a list?).
Is splitting the data in a “filter per collection” approach something realistic to do? - If everything is ATM within a my_collection, send everything to my_collection_by_country, my_collection_by_city, my_collection_by_nFilter.
Thanks in advance!