ChristopherRabotin
Bungiesearch may index undesired models onto another index
This bug is yet to be confirmed.
Situation
We have two indices. One which should only have a model called RawArticle and the other one which has RawArticle as well as six other models. This should is because of how the ModelIndex modules are coded. However, retrieving the mapping and results from the shorter index seems to be able to return models which should only be indexed on the longer index.
Why is this not yet confirmed?
We play around with indexes a lot. It is very likely that the shorter index initially had all the other models, either when the mapping was created or when we started indexing.
How to test this in the future?
The tests should (or already have?) multiple modules with ModelIndex-es. One of those modules should have a model which is in both modules/indexes. We should then check that searching for items which should not be indexed on that second index returns zero results (or an ES error?).
