Adding new data to existing records is ignored about gatsby-plugin-algolia HOT 3 CLOSED

That's a simple enough fix. It may be worth a callout in the readme, but since I'm the first to run across this it may just confuse folks. Thanks for the help!

from gatsby-plugin-algolia.

What you could also do is in the transformer, add some &version=123 to the contentDigest, which then would imply to the rest of indexing that all objects have updated, and thus will index as you'd expect

from gatsby-plugin-algolia.

I haven't come across that feature request yet, I think the easiest would be to locally index it once to a different index, then use moveIndex to replace your production index with the locally created index with all information in it. Then from that point on everything should work as expected.

We're relying on contentDigest of the nodes, so that wouldn't have changed in your case, unless you change the nodes as well in Gatsby, which could be an alternative option.

from gatsby-plugin-algolia.