-
Notifications
You must be signed in to change notification settings - Fork 215
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
Version 1.7.1 doesn't support existing index. #167
Comments
Can you please try:
Please send the log if unsuccessful |
It works now. Maybe, that's because I used existing index. Thanks a lot. |
Good news. The initial import has been changed in release 1.7.1 see #47. |
I'm a new user and I just did it and I found that everything has been synced already after I set it up. |
Can this issue be closed? |
Yes. However, I have one more question. Is it possible to setup river on existing index? |
Having the same problem with existing index with predefined mapping for parent/child relationship. It simply wont index child documents at all. It says _riverstatus 1 INITIAL_IMPORT_FAILED, I was managed to get this working with 1.7.0 without problems, but 1.7.0 was indexing more documents that collection have :) Would be glad to get any explanation how to fix it. |
there is also problem with closing mongoriver after deleting record from _river/ index It is looping like this until I restart elastic |
I got that error too when I set it up on existing index. |
@vglafirov Initial import has been currently changed in 1.7.1 to use the collection data and it actually force you to use an index empty... That's probably not ideal in your scenario. |
Should I rollback to 1.7.0 then? |
That's probably the best for now. I will at this issue for the next release. |
Great, thanks |
Let me explain what's happening... As I said the initial import has been changed in 1.7.1 (see #47) , it now uses the collection data speed up to the process then use oplog.rs collection.
They are few issues here:
With the current release 1.7.1 you might be able to by-pass the issue using [1] - 57fc1c7 |
Thank you for explanation. 👍 Thanks a lot. |
I'm using ES 0.90.5
Mongo 2.4.6
Mongo-River: 1.7.1
OS: Mac 10.8.5
I've setup replicatset and made sure that there's no existing mapping in ES
by running this command
Then I created the mapping by the following command
But it didn't work like I expected. I tried to insert new document into
the collection but it didn't copy to elasticsearch.
Here is the elasticsearch.log
Thank you.
The text was updated successfully, but these errors were encountered: