Understanding the indexRelations setting

[aaronbushnell]

We have a site that leverages Scout for a number of content types and Algolia indexes. Recently, when a content editor would save an entry, we noticed Scout was causing the save process to hang for a long time.

I learned about indexRelations from #173 and #223, and setting this to false made a dramatic improvement for our case! However, I'm not totally certain I understand what disabling this option does.

Here's our situation:

• We have two content types (Services and Locations)
• Locations are sent to Algolia via Scout
• Each location in the index shows related "services"

If I change the name of a "Service" entry it doesn't seem to update that name on the "Location" records whether indexRelations is set to true or false. I assumed true would mean that update would have been made across the relevant location records while false would prevent that. Is that not the case? Am I misunderstanding this option?

[aaronbushnell]

Looks like saving a "Service" entry does update the "Location" record where it's referenced when indexRelations is true! Algolia must have delayed the change a bit so it didn't appear to have any effect initially.