Priority: Major - P3
Affects Version/s: 2.6.11, 3.0.7, 3.2.0-rc3
Fix Version/s: None
We're regularly running into the limitation on 64 indexes per collection. Due to the nature in which we store our customer data, which is highly dynamic, we often run into the need to individually index more than 64 fields.
This is greatly impacting performance capabilities for our use case.
Given the type of metadata we store with each record, the indexes have been a great way for us to ensure absolute performance when the users are filtering their dynamic content.
Due to the above, when we fully index every sortable and filterable field for users, we end up having an index size that is 6-10% of the collection size.
Realizing that we can't do compound indexes past 2, there's still tons of value for us in creating significantly more indexes when needed.
Please up the limit from 64 to at least 256, possibly 512.