Skip to content
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

Open
dfeyer opened this issue Feb 1, 2017 · 5 comments
Open

Create one index per site #177

dfeyer opened this issue Feb 1, 2017 · 5 comments

Comments

@dfeyer
Copy link
Contributor

dfeyer commented Feb 1, 2017

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, ...

@kdambekalns
Copy link
Member

This refers to multi-site setups, i.e. where more than one site is in the same instance of Neos, right?

@daniellienert
Copy link
Contributor

Yes, that's the use case.

@dfeyer
Copy link
Contributor Author

dfeyer commented 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
Copy link
Member

True, but… we could still allow to define "scopes" for "sub-trees", no?

@dfeyer
Copy link
Contributor Author

dfeyer commented Apr 7, 2019

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 ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants