Sylvain Utard

Hmmmmm, that's indeed weird. Did you index at least one object after changing the settings? They are set at the first add/delete object.

> Oh boy, that's interesting... I spent 2hs believing that Venue.reindex should be doing that... I just updated an object and I can see the ranking settings correctly now. Actually,...

> Seems like a good idea, I am struggling to understand where I am supposed to connect with github ? There is no such action from the plugin interface. yes,...

@jamiewilson you're right, we don't collect Unstars for now; not sure that explains it all because the diff seems pretty high :/ Need to dig more into githubarchives.org data to...

@jamiewilson ahah indeed :) We use the number of stars for relevance purpose, so it's not a big deal if the values are not super up-to-date but better if we...

Yes it's more complex than just a lambda evaluation, the underlying "cache" that avoids to call the `{get,set}_settings` endpoint need to be redesigned to add that feature.

> Without the lambda support, how do we get the one-index-per-language to work? > > https://www.algolia.com/doc/guides/search/multilingual-search#option-1-one-index-per-language In such case (because from what I understand each object has its own language)...

> I have a similar use case, where every organization has n documents. An organization should only be searching in an index where it's own documents are present. Actually @phildionne,...

> Any thoughts on a better way to handle this? Or are we pushing this gem to it's limits with our implementation? Thanks! Thanks for sharing that use-case with us....

That's weird, do you have the associated backtrace? Is it raised from the `record.delay.{remove_from_,}index!` methods?