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

Use Batch Operation When Indexing Existing Collection #15

Closed
jamescarr opened this issue Jul 1, 2012 · 4 comments
Closed

Use Batch Operation When Indexing Existing Collection #15

jamescarr opened this issue Jul 1, 2012 · 4 comments
Milestone

Comments

@jamescarr
Copy link
Collaborator

Currently indexing an existing collection can take ages thanks to how slow it is indexing one document at a time. Performance would likely be significantly improved if we index documents in batches of 10 or more at a time.

@martindale
Copy link

+1 for this feature.

@gabrielmancini
Copy link
Contributor

+1

@brandom
Copy link

brandom commented Jul 18, 2014

@jamescarr I have implemented this and would like to submit a PR. After reading your contributing section of the README it states that all PRs should be branched from develop but that branch is currently 33 commits ahead and 79 commits behind master. Should I just submit the PR against master?

@taterbase
Copy link
Owner

This issue has been moved to mongoosastic#1

chetverikov referenced this issue in chetverikov/mongoosastic Mar 27, 2015
…hydrate-hits

Cubuzoa/feature/hydrate hits
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants