Problem in CouchDB integration

Elastic Stack Elasticsearch
1

Hi everyody,

I want to integrate CouchDB into elastic search follwing the tutorial of
elastic search web site
(http://www.elasticsearch.org/tutorials/2010/08/01/couchb-integration.html).
Other wise, when I run this command in the terminal :
curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"user" : "Sellami",
"password" : "12345",
"host" : 127.0.0.1,
"port" : 5984,
"db" : "mycouchshop",
"ignore_attachments":true,
"filter" : null
}
}'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting
comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami

2 
      curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
          "type" : "couchdb",
          "couchdb" : {
              "user" : "Sellami",
              "password" : "12345",
              "host" : 127.0.0.1,
              "port" : 5984,
              "db" : "mycouchshop",
              "ignore_attachments":true,
              "filter" : null
          }
      }'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested: JsonParseException[Unexpected character ('.' (code 46)): was expecting comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Shouldn't the value for your "host" key be quoted? It's a string.

Cheers,
Dan

Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

3

Hi Dan,
Thank you for your quick response. However, your suggestion did not work.
This is the error message :

{"error":"MapperParsingException[Failed to parse [couchdb.host]]; nested:
NumberFormatException[multiple points]; ","status":400}.

Hence, I think that the host shoul not be as a string.

Regards,
Rami Sellami

Le mercredi 18 juillet 2012 18:46:42 UTC+2, Dan Fairs a écrit :

      curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
          "type" : "couchdb",
          "couchdb" : {
              "user" : "Sellami",
              "password" : "12345",
              "host" : 127.0.0.1,
              "port" : 5984,
              "db" : "mycouchshop",
              "ignore_attachments":true,
              "filter" : null
          }
      }'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting
comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Shouldn't the value for your "host" key be quoted? It's a string.

Cheers,
Dan

Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

4

Hi Dan,
Thank you for your quick response. However, your suggestion did not work.
This is the error message :

{"error":"
MapperParsingException[Failed to parse [couchdb.host]]; nested:
NumberFormatException[multiple points]; ","status":400}.

Hence, I think that the host shoul not be as a string.

Regards,
Rami Sellami

5

Hi Dan,
Thank you for your quick response. However, your suggestion did not work. This is the error message :

{"error":"
MapperParsingException[Failed to parse [couchdb.host]]; nested: NumberFormatException[multiple points]; ","status":400}.

Hence, I think that the host shoul not be as a string.

Well - my system POSTs data like this when it creates a CouchDB river:

{"index": {"bulk_timeout": "100ms", "index": "unittest_2012_22", "type": "docs", "bulk_size": "100"}, "couchdb": {"filter": null, "host": "localhost", "ignore_attachments": true, "db": "unittest_2012_22", "port": 5984}, "type": "couchdb"}

Perhaps try the hostname?

Cheers,
Dan

Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

6

Sorry Dan, but what do you mean by "hostname"?

Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :

Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of
Elasticsearch web site (
Elasticsearch Platform — Find real-time answers at scale | Elastic).
Other wise, when I run this command in the terminal :
curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"user" : "Sellami",
"password" : "12345",
"host" : 127.0.0.1,
"port" : 5984,
"db" : "mycouchshop",
"ignore_attachments":true,
"filter" : null
}
}'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting
comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami

7

Well - my system POSTs data like this when it creates a CouchDB river:

Apologies - it's a PUT not POST, to http://127.0.0.1:9200/_river/unittest_2012_22/_meta

Cheers,
Dan

{"index": {"bulk_timeout": "100ms", "index": "unittest_2012_22", "type": "docs", "bulk_size": "100"}, "couchdb": {"filter": null, "host": "localhost", "ignore_attachments": true, "db": "unittest_2012_22", "port": 5984}, "type": "couchdb"}

Perhaps try the hostname?

Cheers,
Dan

Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

--
Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

8

On 18 Jul 2012, at 18:17, rami sellami wrote:

Sorry Dan, but what do you mean by "hostname"?

Take a look at the sample - I used "localhost" rather than "127.0.0.1".

Cheers,
Dan

Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :
Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of Elasticsearch web site (Elasticsearch Platform — Find real-time answers at scale | Elastic). Other wise, when I run this command in the terminal :
curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"user" : "Sellami",
"password" : "12345",
"host" : 127.0.0.1,
"port" : 5984,
"db" : "mycouchshop",
"ignore_attachments":true,
"filter" : null
}
}'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested: JsonParseException[Unexpected character ('.' (code 46)): was expecting comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami

--
Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

9

It did not work. I think that it is a configuration problem and I do not
know how to solve it. :frowning:

2012/7/18 Dan Fairs dan.fairs@gmail.com

On 18 Jul 2012, at 18:17, rami sellami wrote:

Sorry Dan, but what do you mean by "hostname"?

Take a look at the sample - I used "localhost" rather than "127.0.0.1".

Cheers,
Dan

Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :

Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of
Elasticsearch web site (http://www.elasticsearch.org/**
tutorials/2010/08/01/couchb-**integration.htmlhttp://www.elasticsearch.org/tutorials/2010/08/01/couchb-integration.html).
Other wise, when I run this command in the terminal :
curl -XPUT 'http://localhost:9200/_river/**my_es_idx/_metahttp://localhost:9200/_river/my_es_idx/_meta'
-d '{
"type" : "couchdb",
"couchdb" : {
"user" : "Sellami",
"password" : "12345",
"host" : 127.0.0.1,
"port" : 5984,
"db" : "mycouchshop",
"ignore_attachments":true,
"filter" : null
}
}'

I get this errorr message :

{"error":"**MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting
comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami

--
Dan Fairs | dan.fairs@gmail.com | @danfairs | www.fezconsulting.com

--
Cordialement,
Rami Sellami

10

Hi all,
Please help me, I stilli have the same problem!!! I do not how to solve it

Thanks in advance

Best regard,
Rami Sellmai
Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :

Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of
Elasticsearch web site (
Elasticsearch Platform — Find real-time answers at scale | Elastic).
Other wise, when I run this command in the terminal :
curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"user" : "Sellami",
"password" : "12345",
"host" : 127.0.0.1,
"port" : 5984,
"db" : "mycouchshop",
"ignore_attachments":true,
"filter" : null
}
}'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting
comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami

11

I suggest one thing:

Copy your JSON content (aka your river definition), paste it into
http://jsonformatter.curiousconcept.com/
http://jsonformatter.curiousconcept.com/ and click on process.

And see if there are errors.

If there are errors, it could be a bad encoding character.

BTW, are you sure you are pasting the real curl command ?

David

Le 20 juillet 2012 à 12:11, rami sellami sel.rami@gmail.com a écrit :

Hi all,
Please help me, I stilli have the same problem!!! I do not how to solve it

Thanks in advance

Best regard,
Rami Sellmai
Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :

Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of
Elasticsearch web site (
Elasticsearch Platform — Find real-time answers at scale | Elastic).
Other wise, when I run this command in the terminal :
curl -XPUT '
http://www.elasticsearch.org/tutorials/2010/08/01/couchb-integration.html
http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type" : "couchdb",
"couchdb" : {
"user" : "Sellami",
"password" : "12345",
"host" : 127.0.0.1,
"port" : 5984,
"db" : "mycouchshop",
"ignore_attachments":true,
"filter" : null
}
}'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting comma
to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]];
","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami
http://localhost:9200/_river/my_es_idx/_meta

http://localhost:9200/_river/my_es_idx/_meta

--
David Pilato
http://dev.david.pilato.fr/
Twitter : @dadoonet

12

Dear David,

thank you for answering me. It doesn't work [?].
I tried this also
sellami@ubuntu:~$ curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta'
-d '{
"type":"couchdb",
"couchdb":{
"user":"Sellami",
"password":"12345",
"host":"127.0.0.1",
"port":5984,
"db":"mycouchshop",
"ignore_attachments":true,
"filter":null
}
}'

{"error":"MapperParsingException[Failed to parse [couchdb.host]]; nested:
NumberFormatException[multiple points]; ","status":400}

Have you got any other suggestion??

Regard,
Rami Sellami

2012/7/20 David Pilato david@pilato.fr

**

I suggest one thing:

Copy your JSON content (aka your river definition), paste it into
http://jsonformatter.curiousconcept.com/ and click on process.

And see if there are errors.

If there are errors, it could be a bad encoding character.

BTW, are you sure you are pasting the real curl command ?

David

Le 20 juillet 2012 à 12:11, rami sellami sel.rami@gmail.com a écrit :

Hi all,
Please help me, I stilli have the same problem!!! I do not how to solve it

Thanks in advance

Best regard,
Rami Sellmai
Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :

Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of
Elasticsearch web site ( Elasticsearch Platform — Find real-time answers at scale | Elastic).
Other wise, when I run this command in the terminal :
curl -XPUT 'http://www.elasticsearch.org/tutorials/2010/08/01/couchb-integration.html http://localhost:9200/_river/my_es_idx/_meta'
-d '{

          "type" : "couchdb",
          "couchdb" : {
              "user" : "Sellami",
              "password" : "12345",
              "host" : 127.0.0.1,
              "port" : 5984,
              "db" : "mycouchshop",
              "ignore_attachments":true,
              "filter" : null
          }
      }'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested:
JsonParseException[Unexpected character ('.' (code 46)): was expecting
comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami
http://localhost:9200/_river/my_es_idx/_meta

http://localhost:9200/_river/my_es_idx/_meta

--
David Pilato
http://dev.david.pilato.fr/
Twitter : @dadoonet

--
Cordialement,
Rami Sellami

13

Use localhost instead of 127.0.0.1

David :wink:
Twitter : @dadoonet / @elasticsearchfr

Le 20 juil. 2012 à 15:23, rami sellami sel.rami@gmail.com a écrit :

Dear David,

thank you for answering me. It doesn't work <343.gif>.
I tried this also
sellami@ubuntu:~$ curl -XPUT 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type":"couchdb",
"couchdb":{
"user":"Sellami",
"password":"12345",
"host":"127.0.0.1",
"port":5984,
"db":"mycouchshop",
"ignore_attachments":true,
"filter":null
}
}'

{"error":"MapperParsingException[Failed to parse [couchdb.host]]; nested: NumberFormatException[multiple points]; ","status":400}

Have you got any other suggestion??

Regard,
Rami Sellami

2012/7/20 David Pilato david@pilato.fr
I suggest one thing:

Copy your JSON content (aka your river definition), paste it into http://jsonformatter.curiousconcept.com/ and click on process.

And see if there are errors.

If there are errors, it could be a bad encoding character.

BTW, are you sure you are pasting the real curl command ?

David

Le 20 juillet 2012 à 12:11, rami sellami sel.rami@gmail.com a écrit :

Hi all,
Please help me, I stilli have the same problem!!! I do not how to solve it

Thanks in advance

Best regard,
Rami Sellmai
Le mercredi 18 juillet 2012 18:38:24 UTC+2, rami sellami a écrit :
Hi everyody,

I want to integrate CouchDB into Elasticsearch follwing the tutorial of Elasticsearch web site ( Elasticsearch Platform — Find real-time answers at scale | Elastic). Other wise, when I run this command in the terminal :
curl -XPUT ' http://localhost:9200/_river/my_es_idx/_meta' -d '{

          "type" : "couchdb",
          "couchdb" : {
              "user" : "Sellami",
              "password" : "12345",
              "host" : 127.0.0.1,
              "port" : 5984,
              "db" : "mycouchshop",
              "ignore_attachments":true,
              "filter" : null
          }
      }'

I get this errorr message :

{"error":"MapperParsingException[Failed to parse]; nested: JsonParseException[Unexpected character ('.' (code 46)): was expecting comma to separate OBJECT entries\n at [Source: [B@78f0ec3d; line: 6, column: 24]]; ","status":400}

Could you please help me?

Thanks in advance :slight_smile:

Best regards,
Rami Sellami

--
David Pilato
http://dev.david.pilato.fr/
Twitter : @dadoonet

--
Cordialement,
Rami Sellami

14

On Fri, 2012-07-20 at 15:23 +0200, rami sellami wrote:

Dear David,

thank you for answering me. It doesn't work .
I tried this also
sellami@ubuntu:~$ curl -XPUT
'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type":"couchdb",
"couchdb":{
"user":"Sellami",
"password":"12345",
"host":"127.0.0.1",
"port":5984,
"db":"mycouchshop",
"ignore_attachments":true,
"filter":null
}
}'

Your 'host' field is mapped as a number, which means that if you try to
put 127.0.0.1 into it, it fails, because that is clearly not a number.

clint

15

@ David, I tried localhost but didn't work. I think localhost is proper to
the elasticsearch.
@clint Have you got a suggestion??

2012/7/20 Clinton Gormley clint@traveljury.com

On Fri, 2012-07-20 at 15:23 +0200, rami sellami wrote:

Dear David,

thank you for answering me. It doesn't work .
I tried this also
sellami@ubuntu:~$ curl -XPUT
'http://localhost:9200/_river/my_es_idx/_meta' -d '{
"type":"couchdb",
"couchdb":{
"user":"Sellami",
"password":"12345",
"host":"127.0.0.1",
"port":5984,
"db":"mycouchshop",
"ignore_attachments":true,
"filter":null
}
}'

Your 'host' field is mapped as a number, which means that if you try to
put 127.0.0.1 into it, it fails, because that is clearly not a number.

clint

--
Cordialement,
Rami Sellami

16

On Fri, 2012-07-20 at 15:40 +0200, rami sellami wrote:

@ David, I tried localhost but didn't work. I think localhost is
proper to the elasticsearch.
@clint Have you got a suggestion??

Yes. Fix your mapping for that field. It should be:

{ type: "string", "index": "not_analyzed"}

2012/7/20 Clinton Gormley clint@traveljury.com
On Fri, 2012-07-20 at 15:23 +0200, rami sellami wrote:
> Dear David,
>
> thank you for answering me. It doesn't work .
> I tried this also
> sellami@ubuntu:~$ curl -XPUT
> 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
> "type":"couchdb",
> "couchdb":{
> "user":"Sellami",
> "password":"12345",
> "host":"127.0.0.1",
> "port":5984,
> "db":"mycouchshop",
> "ignore_attachments":true,
> "filter":null
> }
> }'

    Your 'host' field is mapped as a number, which means that if
    you try to
    put 127.0.0.1 into it, it fails, because that is clearly not a
    number.
    
    clint

--
Cordialement,
Rami Sellami

17

Hum. I see.

So Rami first send a river creation in _river/my_es_idx with hostname starting with number.
So ES tried to dynamically map it to Number, but fails.
Then he tried to push a new river definition with "localhost" and it fails also as the mapping already exists.

Is it what you have in mind Clint ?

If so, may I suggest to Rani to:

  1. Delete the _river index (and all its associated mappings)
  2. Send a river creation document with "localhost" as "host"

Then if really needed, he could push an update for the river with "172.0.0.1". This host will be read as a String by ES, because mapping will already exist.

It should work, isn't it ?

Cheers
David.

-----Message d'origine-----
De : elasticsearch@googlegroups.com
[mailto:elasticsearch@googlegroups.com] De la part de Clinton Gormley
Envoyé : vendredi 20 juillet 2012 15:59
À : elasticsearch@googlegroups.com
Objet : Re: Problem in CouchDB integration

On Fri, 2012-07-20 at 15:40 +0200, rami sellami wrote:

@ David, I tried localhost but didn't work. I think localhost is
proper to the elasticsearch.
@clint Have you got a suggestion??

Yes. Fix your mapping for that field. It should be:

{ type: "string", "index": "not_analyzed"}

2012/7/20 Clinton Gormley clint@traveljury.com
On Fri, 2012-07-20 at 15:23 +0200, rami sellami wrote:
> Dear David,
>
> thank you for answering me. It doesn't work .
> I tried this also
> sellami@ubuntu:~$ curl -XPUT
> 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
> "type":"couchdb",
> "couchdb":{
> "user":"Sellami",
> "password":"12345",
> "host":"127.0.0.1",
> "port":5984,
> "db":"mycouchshop",
> "ignore_attachments":true,
> "filter":null
> }
> }'

    Your 'host' field is mapped as a number, which means that if
    you try to
    put 127.0.0.1 into it, it fails, because that is clearly not

a

    number.

    clint

--
Cordialement,
Rami Sellami

18

On Sat, 2012-07-21 at 00:15 +0200, David Pilato wrote:

Hum. I see.

So Rami first send a river creation in _river/my_es_idx with hostname starting with number.
So ES tried to dynamically map it to Number, but fails.
Then he tried to push a new river definition with "localhost" and it fails also as the mapping already exists.

Is it what you have in mind Clint ?

Correct

If so, may I suggest to Rani to:

  1. Delete the _river index (and all its associated mappings)
  2. Send a river creation document with "localhost" as "host"

Then if really needed, he could push an update for the river with "172.0.0.1". This host will be read as a String by ES, because mapping will already exist.

It should work, isn't it ?

Yes

Or, even better (but more work) - delete the current index, create a new
index with the proper mappings, then recreate the river. That way you
can avoid more datatype mismatches.

clint

Cheers
David.

-----Message d'origine-----
De : elasticsearch@googlegroups.com
[mailto:elasticsearch@googlegroups.com] De la part de Clinton Gormley
Envoyé : vendredi 20 juillet 2012 15:59
À : elasticsearch@googlegroups.com
Objet : Re: Problem in CouchDB integration

On Fri, 2012-07-20 at 15:40 +0200, rami sellami wrote:

@ David, I tried localhost but didn't work. I think localhost is
proper to the elasticsearch.
@clint Have you got a suggestion??

Yes. Fix your mapping for that field. It should be:

{ type: "string", "index": "not_analyzed"}

2012/7/20 Clinton Gormley clint@traveljury.com
On Fri, 2012-07-20 at 15:23 +0200, rami sellami wrote:
> Dear David,
>
> thank you for answering me. It doesn't work .
> I tried this also
> sellami@ubuntu:~$ curl -XPUT
> 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
> "type":"couchdb",
> "couchdb":{
> "user":"Sellami",
> "password":"12345",
> "host":"127.0.0.1",
> "port":5984,
> "db":"mycouchshop",
> "ignore_attachments":true,
> "filter":null
> }
> }'

    Your 'host' field is mapped as a number, which means that if
    you try to
    put 127.0.0.1 into it, it fails, because that is clearly not

a

    number.

    clint

--
Cordialement,
Rami Sellami

19

Dear all,

Now it works (ouuuf). So I deleted the river index and I used this command
:

curl -XPUT 'localhost:9200/_river/toto1/_meta' -d '{
   "type" : "couchdb",
   "couchdb" : {
       "host" : "localhost",
       "port" : 5984,
       "db" : "toto1",
       "filter" : null
   },
   *"index" : {
       "index" : "toto1",
       "type" : "toto1",
       "bulk_size" : "100",
       "bulk_timeout" : "10ms"
   }*

}'

So now it is fine.

Thank you very much Clint, David and Dan.

Best regards.
Rami

2012/7/21 Clinton Gormley clint@traveljury.com

On Sat, 2012-07-21 at 00:15 +0200, David Pilato wrote:

Hum. I see.

So Rami first send a river creation in _river/my_es_idx with hostname
starting with number.
So ES tried to dynamically map it to Number, but fails.
Then he tried to push a new river definition with "localhost" and it
fails also as the mapping already exists.

Is it what you have in mind Clint ?

Correct

If so, may I suggest to Rani to:

  1. Delete the _river index (and all its associated mappings)
  2. Send a river creation document with "localhost" as "host"

Then if really needed, he could push an update for the river with
"172.0.0.1". This host will be read as a String by ES, because mapping will
already exist.

It should work, isn't it ?

Yes

Or, even better (but more work) - delete the current index, create a new
index with the proper mappings, then recreate the river. That way you
can avoid more datatype mismatches.

clint

Cheers
David.

-----Message d'origine-----
De : elasticsearch@googlegroups.com
[mailto:elasticsearch@googlegroups.com] De la part de Clinton Gormley
Envoyé : vendredi 20 juillet 2012 15:59
À : elasticsearch@googlegroups.com
Objet : Re: Problem in CouchDB integration

On Fri, 2012-07-20 at 15:40 +0200, rami sellami wrote:

@ David, I tried localhost but didn't work. I think localhost is
proper to the elasticsearch.
@clint Have you got a suggestion??

Yes. Fix your mapping for that field. It should be:

{ type: "string", "index": "not_analyzed"}

2012/7/20 Clinton Gormley clint@traveljury.com
On Fri, 2012-07-20 at 15:23 +0200, rami sellami wrote:
> Dear David,
>
> thank you for answering me. It doesn't work .
> I tried this also
> sellami@ubuntu:~$ curl -XPUT
> 'http://localhost:9200/_river/my_es_idx/_meta' -d '{
> "type":"couchdb",
> "couchdb":{
> "user":"Sellami",
> "password":"12345",
> "host":"127.0.0.1",
> "port":5984,
> "db":"mycouchshop",
> "ignore_attachments":true,
> "filter":null
> }
> }'

    Your 'host' field is mapped as a number, which means that if
    you try to
    put 127.0.0.1 into it, it fails, because that is clearly not

a

    number.

    clint

--
Cordialement,
Rami Sellami

--
Cordialement,
Rami Sellami