-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create one index per site #177
Comments
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 |
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, ...
The text was updated successfully, but these errors were encountered: