Flowpack.ElasticSearch.ContentRepositoryAdaptor
Flowpack.ElasticSearch.ContentRepositoryAdaptor copied to clipboard
Create one index per site
Currently we use only one index for all sites, that can make some scoring feature of Elastic to not work as expected, by ex. word frequency will take in account other site, ...
This refers to multi-site setups, i.e. where more than one site is in the same instance of Neos, right?
Yes, that's the use case.
Thinking about this issue, because I'm in the "one index per dimensions combination" ... it can be done, but we will couple this package with Neos ... a site is nothing for the ContentRepository :(
True, but… we could still allow to define "scopes" for "sub-trees", no?
I restart working on the "one index per dimensions preset", and I will try to experiment a bit in implementing a IndexNameSelectorInterface
that will make this possible ... but first let's make the current PR stable before breaking everything again ;)