You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been going over our Algolia operations limit recently, and noticed that ~51% of our operations count is going to reindexing. We run a full reindex nightly to capture deletions.
Could we implement something like algolia/gatsby-plugin-algolia#27 which generates a changeset based on an "updated at" field to save on operations? I'd be happy to code up the pull request, unless someone is already working on it.
The text was updated successfully, but these errors were encountered:
Hey @gburgett, thanks for creating this issue! You're welcome to go ahead and create a pull request. However we can't assure you for the moment a review and release date. If that's still okay with you we're looking forward your contribution.
Hello!
We've been going over our Algolia operations limit recently, and noticed that ~51% of our operations count is going to reindexing. We run a full reindex nightly to capture deletions.
Could we implement something like algolia/gatsby-plugin-algolia#27 which generates a changeset based on an "updated at" field to save on operations? I'd be happy to code up the pull request, unless someone is already working on it.
The text was updated successfully, but these errors were encountered: