Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getRemoteIndex does not seem to resolve on > 1000 entries indices #16

Closed
regisphilibert opened this issue Apr 25, 2019 · 1 comment
Closed

Comments

@regisphilibert
Copy link

It seems getRemoteIndex does not resolve with indices holding over 1000 entries.

Therefore, oldIndex remains undefined and the script will then assume there is no entry in the oldIndex and push every entries from the newIndex to Algolia without checking for changes first.

chrisdmacrae added a commit that referenced this issue Jul 23, 2020
…ments

Fixed #16 getRemoteIndex does not seem to resolve …
@chrisdmacrae
Copy link
Owner

@regisphilibert this will be fixed today in 0.3.18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants