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

Data is re-imported on index re-created after db.collection.remove() and db.dropDatabase() #250

Closed
golspe opened this issue Apr 8, 2014 · 1 comment

Comments

@golspe
Copy link

golspe commented Apr 8, 2014

I have the following settings turned on:

"secondary_read_preference": true,
"import_all_collections": true,
"skip_initial_import": true

I perform the following steps:

  1. curl XDELETE _river index
  2. curl xDELETE ES index
  3. mongo db.collection.remove() and db.dropDatabase()
  4. curl XPUT _river index with aforementioned settings

Why on the re-creation of my indexes does the old data get re-imported? What is the appropriate way to configure/delete the river plugin to remove all ES indexes and corresponding data when data is removed/dropped from Mongo?

@golspe golspe closed this as completed Apr 9, 2014
@golspe
Copy link
Author

golspe commented Apr 9, 2014

Closed as I created new version of this issue - #251

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

1 participant