You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, ...
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 :(
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 ;)
Activity
kdambekalns commentedon Mar 1, 2017
This refers to multi-site setups, i.e. where more than one site is in the same instance of Neos, right?
daniellienert commentedon Mar 1, 2017
Yes, that's the use case.
dfeyer commentedon Jul 15, 2017
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 :(
kdambekalns commentedon Jul 17, 2017
True, but… we could still allow to define "scopes" for "sub-trees", no?
dfeyer commentedon Apr 7, 2019
I restart working on the "one index per dimensions preset", and I will try to experiment a bit in implementing a
IndexNameSelectorInterfacethat will make this possible ... but first let's make the current PR stable before breaking everything again ;)