Slaves config : facets on a slave indice about search-bundle HOT 7 CLOSED

Also i get an error A slave index is already slave of another index whenever i try to reindex after pushing my configuration to algolia, it's pretty annoying, what did I do wrong ?

from search-bundle.

The second issue is probably related to the env, the same slave name is probably used for two envs. I am currently investigating the first one

from search-bundle.

So the issue is, there is no set settings done on the slaves, we can fix that pretty easily but that would mean loosing the ability to customize independently the master and the slave.
Let's keep this issue open, we will probably need to introduce a new annotation

In the meantime the easier way to handle that would be to do a small php script on the side that handle the setSettings

from search-bundle.

What I would expect maybe is being able to configure something like:

slaves = {
  attributesForFaceting = {"macroCategoryTitle", "timeStamp"},
  ranking = {"asc(timeStamp)", "typo","geo","words","filters","proximity","attribute","exact","custom"},
  customRanking = {"asc(finalPrice)"}
}

This way you keep the existing confurations options

from search-bundle.

yes it's a bit more tricky than this because you could have two slaves with two differents set of settings but yes that's the idea

from search-bundle.

@maxiloc What is the conclusion here? Is it something that would need to be changed by Algolia or is it implementation/usage of the indexes that creates this issue?
Can you point me to an example of solution of what you talks about

a small php script on the side that handle the setSettings

from search-bundle.

As @maxiloc explained this is tricky given the current design. We will make sure we allow this kind of use cases by better designing our different abstractions in V3. Labelling this issue to be sure we don't forget your use case. Please bear with us, and sorry about the delay.

from search-bundle.