-
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
Unable to determine mongo collection for indexed document #101
Comments
Hello, You have a couple of options with the current release:
Let me know if the first 2 options work for you. I could also create a new settings Thanks, |
For the mean time I just do a mongo db find in each collection by document id to find the collection it belongs too as I didn't want to have to go update documents but I reckon the settings option is the way to go. |
Thanks, which release will this make it into? |
Hi, That's available in version 1.6.11 just released today. Thanks, On Tuesday, July 16, 2013, Wesley Archbell wrote:
|
Thanks, if i used this version (1.6.11) will it still work with older versions of mongodb and elasticsearch? specifically mongodb version 2.4.4 & ES version 0.90.1? |
Hi, Yes it should be working. Thanks, Sent via BlackBerry by AT&T -----Original Message----- Thanks, if i used this version (1.6.11) will it still work with older versions of mongodb? specifically version 2.4.4? Reply to this email directly or view it on GitHub: |
Ok thanks will give it a try |
One more thing, where is the 'options/include_collection' set in? Which file? |
Hi, In the river settings the wiki should be updated. Thanks, Sent via BlackBerry by AT&T -----Original Message----- One more thing, where is the 'options/include_collection' set in? Which file? Reply to this email directly or view it on GitHub: |
OK Thanks :) |
Ive just tried including the change with the new option with v1.6.11, but i dont see any new field in the source fields.. |
Hi, I will not be able to help before few days (currently on vacations). But you compare / check the example available in HEAD (issues/101 folder). There is also a test case available. Can you also provide your river settings? Thanks, Sent via BlackBerry by AT&T -----Original Message----- Ive just tried including the change with the new option with v1.6.11, but i dont see any new field in the source fields.. Reply to this email directly or view it on GitHub: |
No worries, thanks will check it out. Have a good break man :) |
Hi Richard, when you get back would u be able to have a look at this, I've reviewed the test for fix#101 but my data is not reflecting the change in the document source fields i.e. there is no 'include_collection' field after i have created the river with the options/include_collection setting. I can see that the field is included in one of the rivers by using the head plugin and viewing in browser:
But not present in document source.. Thanks in advance. |
I have successfully re-executed the test located here [1]. [1] - https://github.com/richardwilly98/elasticsearch-river-mongodb/tree/master/resources/issues/101 Thanks, |
Hi richard, sorry for the delay, here is my settings for a river:
|
@wesleyarchbell I have added additional traces. Can you please try the snapshot version available here [1]?
Enable logging for the river:
Please send me ES log file. [1] - https://dl.dropboxusercontent.com/u/64847502/elasticsearch-river-mongodb-1.6.12-SNAPSHOT.zip |
https://www.dropbox.com/s/fm9am817rk3x3nr/elasticsearch.log It seems the include_collection option is empty.. This is the exact curl command i use to create river:
|
@wesleyarchbell from the code it seems that the options section is not recognized. Can you please execute |
The curl comment results in:
|
options should be inside mongodb:
|
Dow! Thanks Richard. |
I am unable to determine which mongo-db collection a document that is indexed in ES belongs too. I have created a unique river for each mongo db collection but they are all indexed under the same index. Is there any way of determining for a given document which mongodb collection it belongs too?
The text was updated successfully, but these errors were encountered: