# \[Ann\] JDBC river 1.0.0.RC1.2

**URL:** <https://discuss.elastic.co/t/ann-jdbc-river-1-0-0-rc1-2/15330>\
**Category:** Elasticsearch\
**Created:** [January 20, 2014, 10:04pm UTC](https://discuss.elastic.co/t/ann-jdbc-river-1-0-0-rc1-2/15330 "2014-01-20T22:04:51Z")\
**Posts on this page:** 3\
**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:** [January 20, 2014, 10:04pm UTC](https://discuss.elastic.co/t/ann-jdbc-river-1-0-0-rc1-2/15330/1 "2014-01-20T22:04:51Z")

</div>

Hi,

just a quick note about a new release of JDBC river.

> **[jprante/elasticsearch-jdbc](https://github.com/jprante/elasticsearch-jdbc)**
>
> elasticsearch-jdbc - JDBC importer for Elasticsearch

Changes

- a series of SQL statements can now be executed at each river cycle
- execution of SQL statements with thread pool size (like connection  
pooling)
- river state saved and loaded at each cycle
- "schedule" parameter with crontab-like specification
- no more "oneshot" strategy
- "poll" parameter removed in favor of "schedule" or "interval"
- "acksql", "acksqlparams" removed in favor of SQL statement series
- "driver" parameter removed
- new parameter "bulk\_flush\_timeout"
- experimental CallableStatement support improved
- river cycle can be executed at once by new REST river induce command
- new REST river state inspection command
- many bug fixes and cleanups

I will rework and extend the documentation pages in the github wiki the  
next days.

Best,

Jörg

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFGiseH6%3Dig5xcVDcV9o%2BOVeR%3D1c4HYFXT4nsSv85QbeQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFGiseH6%3Dig5xcVDcV9o%2BOVeR%3D1c4HYFXT4nsSv85QbeQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Umit\_Seren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/umit_seren/32/44933_2.png) [@Umit\_Seren](https://discuss.elastic.co/u/Umit_Seren)\
**Post date:** [January 21, 2014, 9:12am UTC](https://discuss.elastic.co/t/ann-jdbc-river-1-0-0-rc1-2/15330/2 "2014-01-21T09:12:28Z")

</div>

Great ! Thank you very much.  
I used the oneshot strategry to do the initial indexing and later on used  
indexing on application level to keep the docs in ES and the entities in  
the DB in sync.

What's the new approach now that the oneshot strategy was removed?

I guess I wait until the wiki is updated.

On Monday, January 20, 2014 11:04:51 PM UTC+1, Jörg Prante wrote:

> Hi,
> 
> just a quick note about a new release of JDBC river.
> 
> [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-river-jdbc/)
> 
> Changes
> 
> - a series of SQL statements can now be executed at each river cycle
> - execution of SQL statements with thread pool size (like connection  
> pooling)
> - river state saved and loaded at each cycle
> - "schedule" parameter with crontab-like specification
> - no more "oneshot" strategy
> - "poll" parameter removed in favor of "schedule" or "interval"
> - "acksql", "acksqlparams" removed in favor of SQL statement series
> - "driver" parameter removed
> - new parameter "bulk\_flush\_timeout"
> - experimental CallableStatement support improved
> - river cycle can be executed at once by new REST river induce command
> - new REST river state inspection command
> - many bug fixes and cleanups
> 
> I will rework and extend the documentation pages in the github wiki the  
> next days.
> 
> Best,
> 
> Jörg

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/795a3fba-e994-4f0d-a3a9-3f015cfc917d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/795a3fba-e994-4f0d-a3a9-3f015cfc917d%40googlegroups.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, 1:55am UTC](https://discuss.elastic.co/t/ann-jdbc-river-1-0-0-rc1-2/15330/3 "2017-07-06T01:55:41Z")

</div>


