# Problem with jdbc river with versioning

**URL:** <https://discuss.elastic.co/t/problem-with-jdbc-river-with-versioning/12717>\
**Category:** Elasticsearch\
**Created:** [July 9, 2013, 12:14pm UTC](https://discuss.elastic.co/t/problem-with-jdbc-river-with-versioning/12717 "2013-07-09T12:14:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rishav\_Rohit1](https://avatars.discourse-cdn.com/v4/letter/r/e19b73/32.png) [@Rishav\_Rohit1](https://discuss.elastic.co/u/Rishav_Rohit1)\
**Post date:** [July 9, 2013, 12:14pm UTC](https://discuss.elastic.co/t/problem-with-jdbc-river-with-versioning/12717/1 "2013-07-09T12:14:02Z")

</div>

Hi,

I tried to index MySQL table into ES(version-0.90.1) using jdbc river  
(version-2.2.0). below is my river configuration:

curl -XPUT 'localhost:9200/\_river/geocode/\_meta' -d '{

```
"type":"jdbc",

"jdbc":{

    "strategy":"simple",

    "driver":"com.mysql.jdbc.Driver",

    "url":"jdbc:mysql://######:3306/poc",

    "user":"###",

    "password":"####",

    "sql":"SELECT geonameid as \"_id\", name, asciiname, 

```

alternatenames, latitude, longitude, feature\_class, feature\_code, country,  
cc2, admin1, admin2, admin3, admin4, population, elevation, dem, timezone,  
modification\_date FROM poc.geocode ",

```
    "poll":"1m",

    "digesting" : true

},

"index":{

    "index":"jdbctest",

    "type":"geocode",

    "max_bulk_requests":1,

    "versioning" : true

}

```

}'

This is working fine in the first run and indexes all records from table in  
first run, but is not able to reflect any update made in mysql table and I  
also added large number of new records to the table but again those were  
not indexed in ES.

Also the digest values are not changing in different versions:

```
created: 2013-07-09T11:07:07.887Z

version: 11

digest: VKaM21xTg4mxcqzf1dGleNR5mql3J26v2rBcFURT9/0=

```

After updating some data in table:

created: 2013-07-09T11:07:07.887Z

```
version: 26

digest: VKaM21xTg4mxcqzf1dGleNR5mql3J26v2rBcFURT9/0=

```

I checked this thread also  
[http://elasticsearch-users.115913.n3.nabble.com/JDBC-River-Unexpected-behaviour-with-versioning-td4030453.htmlis](http://elasticsearch-users.115913.n3.nabble.com/JDBC-River-Unexpected-behaviour-with-versioning-td4030453.htmlis) this a known issue with ES jdbc river?

Thanks & Regards,

Rishav Rohit

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:27am UTC](https://discuss.elastic.co/t/problem-with-jdbc-river-with-versioning/12717/2 "2017-07-06T02:27:29Z")

</div>