Elastic Search, CouchDB and River Plugin Problems

Hi,

I posted here but seeing as they don't even have a tag for river-
plugin, it's probably more effective on here.

I'm trying to get ElasticSearch to work, specifically with the River
Plugin. For some reason I just can't get it to work. I've included the
procedure I'm using to try and do it, found here:
http://www.elasticsearch.org/tutorials/2010/08/01/couchb-integration.html

curl -XDELETE 'http://localhost:9200/_all/'
Response:

{"ok":true,"acknowledged":true}
This is so I know I'm working with an empty set of elasticsearch
instances.

I have an existing database, called test and the river plugin has
already been installed. Is there anyway to test to confirm the River
Plugin is installed and running?

I issue the following command:

curl -XPUT 'http://localhost:9200/_river/my_index/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"host" : "localhost",
"port" : 5984,
"db" : "my_couch_db",
"filter" : null
}
}'
my_couch_db is a real database, I see it in Futon. There is a document
in it.

Response:

{"ok":true,"_index":"_river","_type":"my_index","_id":"_meta","_version":
1}
Now at this point, my understanding is elasticseach should be working
as I saw in the tutorial.

I try to query, just to find anything. I go to

http://localhost:9200/my_couch_db/my_couch_db.
Response:

No handler found for uri [/my_couch_db/my_couch_db] and method [GET]
What's weird is when I go to localhost:5984/my_couch_db/__changes

I get {"error":"not_found","reason":"missing"}

Anyone have any idea what part of this I'm screwing up?

Thanks,

--Scott

You need to issue some search requests, the curl you issued after creating the river does not do correlate to any API.
On Friday, May 20, 2011 at 11:36 PM, Scott Feinberg wrote:

Hi,

I posted here but seeing as they don't even have a tag for river-
plugin, it's probably more effective on here.

elasticsearch - CouchDB, Elastic Search, and River Plugin not operating correctly - Stack Overflow

I'm trying to get Elasticsearch to work, specifically with the River
Plugin. For some reason I just can't get it to work. I've included the
procedure I'm using to try and do it, found here:
Elasticsearch Platform — Find real-time answers at scale | Elastic

curl -XDELETE 'http://localhost:9200/_all/'
Response:

{"ok":true,"acknowledged":true}
This is so I know I'm working with an empty set of elasticsearch
instances.

I have an existing database, called test and the river plugin has
already been installed. Is there anyway to test to confirm the River
Plugin is installed and running?

I issue the following command:

curl -XPUT 'http://localhost:9200/_river/my_index/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"host" : "localhost",
"port" : 5984,
"db" : "my_couch_db",
"filter" : null
}
}'
my_couch_db is a real database, I see it in Futon. There is a document
in it.

Response:

{"ok":true,"_index":"_river","_type":"my_index","_id":"_meta","_version":
1}
Now at this point, my understanding is elasticseach should be working
as I saw in the tutorial.

I try to query, just to find anything. I go to

http://localhost:9200/my_couch_db/my_couch_db.
Response:

No handler found for uri [/my_couch_db/my_couch_db] and method [GET]
What's weird is when I go to localhost:5984/my_couch_db/__changes

I get {"error":"not_found","reason":"missing"}

Anyone have any idea what part of this I'm screwing up?

Thanks,

--Scott

As Shay said, there is something wrong. You try to access to

http://localhost:9200/my_couch_db/my_couch_db http://localhost:9200/my_couch_db/my_couch_db

But, you add the river to my_index

curl -XPUT ' http://localhost:9200/_river/my_index/_meta' http://localhost:9200/_river/my_index/_meta'

So I suppose that you should look at http://localhost:9200/my_index/

Try this :

curl -XGET http://localhost:9200/my_index/_search -d '{}'

You should see your document…

Hope this helps,
David.

De : Shay Banon [mailto:shay.banon@elasticsearch.com]
Envoyé : mardi 24 mai 2011 13:45
À : users@elasticsearch.com
Objet : Re: Elastic Search, CouchDB and River Plugin Problems

You need to issue some search requests, the curl you issued after creating the river does not do correlate to any API.

On Friday, May 20, 2011 at 11:36 PM, Scott Feinberg wrote:

Hi,

I posted here but seeing as they don't even have a tag for river-
plugin, it's probably more effective on here.

I'm trying to get ElasticSearch to work, specifically with the River
Plugin. For some reason I just can't get it to work. I've included the
procedure I'm using to try and do it, found here:
http://www.elasticsearch.org/tutorials/2010/08/01/couchb-integration.html

curl -XDELETE 'http://localhost:9200/_all/'
Response:

{"ok":true,"acknowledged":true}
This is so I know I'm working with an empty set of elasticsearch
instances.

I have an existing database, called test and the river plugin has
already been installed. Is there anyway to test to confirm the River
Plugin is installed and running?

I issue the following command:

curl -XPUT 'http://localhost:9200/_river/my_index/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"host" : "localhost",
"port" : 5984,
"db" : "my_couch_db",
"filter" : null
}
}'
my_couch_db is a real database, I see it in Futon. There is a document
in it.

Response:

{"ok":true,"_index":"_river","_type":"my_index","_id":"_meta","_version":
1}
Now at this point, my understanding is elasticseach should be working
as I saw in the tutorial.

I try to query, just to find anything. I go to

http://localhost:9200/my_couch_db/my_couch_db.
Response:

No handler found for uri [/my_couch_db/my_couch_db] and method [GET]
What's weird is when I go to localhost:5984/my_couch_db/__changes

I get {"error":"not_found","reason":"missing"}

Anyone have any idea what part of this I'm screwing up?

Thanks,

--Scott