# \[Ann\] Version 1.2.1 of JDBC river plugin, handling (most) of the JDBC types

**URL:** <https://discuss.elastic.co/t/ann-version-1-2-1-of-jdbc-river-plugin-handling-most-of-the-jdbc-types/8285>\
**Category:** Elasticsearch\
**Created:** [July 2, 2012, 4:17pm UTC](https://discuss.elastic.co/t/ann-version-1-2-1-of-jdbc-river-plugin-handling-most-of-the-jdbc-types/8285 "2012-07-02T16:17:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [July 2, 2012, 4:17pm UTC](https://discuss.elastic.co/t/ann-version-1-2-1-of-jdbc-river-plugin-handling-most-of-the-jdbc-types/8285/1 "2012-07-02T16:17:35Z")

</div>

Hi,

the JDBC river plugin [https://github.com/jprante/elasticsearch-river-jdbc](https://github.com/jprante/elasticsearch-river-jdbc)  
has been updated to version 1.2.1

It is now handling most of the JDBC types as  
of [http://docs.oracle.com/javase/7/docs/api/java/sql/Types.html](http://docs.oracle.com/javase/7/docs/api/java/sql/Types.html)

Also, updating in non river table mode is extended to data changes. That  
is, if data is changed in the SQL DB and the changes are not related to  
index/type/id, an Elasticsearch index update is triggered (which is the  
expected behaviour).

If you find bugs or if you have comments, do not hesitate and open an issue  
at [https://github.com/jprante/elasticsearch-river-jdbc/issues](https://github.com/jprante/elasticsearch-river-jdbc/issues)

All suggestions for improvements are welcome!

Best regards,

Jörg

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [July 2, 2012, 11:00pm UTC](https://discuss.elastic.co/t/ann-version-1-2-1-of-jdbc-river-plugin-handling-most-of-the-jdbc-types/8285/2 "2012-07-02T23:00:08Z")

</div>

Thanks Jorg for all the hard work, much appreciated!

On Mon, Jul 2, 2012 at 6:17 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote:

> Hi,
> 
> the JDBC river plugin [https://github.com/jprante/elasticsearch-river-jdbchas](https://github.com/jprante/elasticsearch-river-jdbchas) been updated to version 1.2.1
> 
> It is now handling most of the JDBC types as of  
> [Types (Java Platform SE 7 )](http://docs.oracle.com/javase/7/docs/api/java/sql/Types.html)
> 
> Also, updating in non river table mode is extended to data changes. That  
> is, if data is changed in the SQL DB and the changes are not related to  
> index/type/id, an Elasticsearch index update is triggered (which is the  
> expected behaviour).
> 
> If you find bugs or if you have comments, do not hesitate and open an  
> issue at [Issues · jprante/elasticsearch-jdbc · GitHub](https://github.com/jprante/elasticsearch-river-jdbc/issues)
> 
> All suggestions for improvements are welcome!
> 
> Best regards,
> 
> Jörg

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [July 2, 2012, 11:16pm UTC](https://discuss.elastic.co/t/ann-version-1-2-1-of-jdbc-river-plugin-handling-most-of-the-jdbc-types/8285/3 "2012-07-02T23:16:07Z")

</div>

I have to thank you, kimchy! Hopefully the JDBC river helps people who need  
Elasticsearch proof-of-concepts from existing amounts of data in SQL DBs.

Best,

Jörg

On Tuesday, July 3, 2012 1:00:08 AM UTC+2, kimchy wrote:

> Thanks Jorg for all the hard work, much appreciated!

---

<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:21am UTC](https://discuss.elastic.co/t/ann-version-1-2-1-of-jdbc-river-plugin-handling-most-of-the-jdbc-types/8285/4 "2017-07-06T03:21:45Z")

</div>