# Does the JSON data type for CouchDB river plugin key-value pairs matter?

**URL:** <https://discuss.elastic.co/t/does-the-json-data-type-for-couchdb-river-plugin-key-value-pairs-matter/7932>\
**Category:** Elasticsearch\
**Created:** [May 31, 2012, 5:20pm UTC](https://discuss.elastic.co/t/does-the-json-data-type-for-couchdb-river-plugin-key-value-pairs-matter/7932 "2012-05-31T17:20:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pulkitsinghal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pulkitsinghal/32/802_2.png) [@pulkitsinghal](https://discuss.elastic.co/u/pulkitsinghal)\
**Post date:** [May 31, 2012, 5:20pm UTC](https://discuss.elastic.co/t/does-the-json-data-type-for-couchdb-river-plugin-key-value-pairs-matter/7932/1 "2012-05-31T17:20:30Z")

</div>

A few thing are at odds in the JSON representation in the CouchDB River  
plugin's readme  
([https://github.com/elasticsearch/elasticsearch-river-couchdb](https://github.com/elasticsearch/elasticsearch-river-couchdb)).

# For example:

# {"port" : 443}

# Versus:

# {"bulk\_size" : "100"}

Q1) Why is one a number and the other a string? Does it not matter?

# Another example:

# "ignore\_attachments" : true

# Versus:

# "no\_verify" : "true"

Q2) Why is one a boolean and the other a string? Does it not matter?

I just want to be super sure that I get my config right w/o any latent bugs  
surfacing later 🙂

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 31, 2012, 6:36pm UTC](https://discuss.elastic.co/t/does-the-json-data-type-for-couchdb-river-plugin-key-value-pairs-matter/7932/2 "2012-05-31T18:36:41Z")

</div>

IMHO, it's best to use the real type for each field.  
As far as I can see, no\_verify is a boolean. So "no\_verify" : true is better.

Same for bulk size which should be {"bulk\_size" : 100}.

HTH  
David

Le 31 mai 2012 à 19:20, pulkitsinghal [pulkitsinghal@gmail.com](mailto:pulkitsinghal@gmail.com) a écrit :

> A few thing are at odds in the JSON representation in the CouchDB River plugin's readme ([GitHub - elastic/elasticsearch-river-couchdb: CouchDB River Plugin for elasticsearch (STOPPED)](https://github.com/elasticsearch/elasticsearch-river-couchdb)).
> 
> # For example:
> 
> # {"port" : 443}
> 
> # Versus:
> 
> # {"bulk\_size" : "100"}
> 
> Q1) Why is one a number and the other a string? Does it not matter?
> 
> # Another example:
> 
> # "ignore\_attachments" : true
> 
> # Versus:
> 
> # "no\_verify" : "true"
> 
> Q2) Why is one a boolean and the other a string? Does it not matter?
> 
> I just want to be super sure that I get my config right w/o any latent bugs surfacing later 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:26am UTC](https://discuss.elastic.co/t/does-the-json-data-type-for-couchdb-river-plugin-key-value-pairs-matter/7932/3 "2017-07-06T03:26:08Z")

</div>

Closed on July 6, 2017, 3:26am UTC