[Ann] JDBC river 1.0.0.RC1.2

Elastic Stack Elasticsearch
1

Hi,

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

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.
To view this discussion on the web visit 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.

2

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

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.
To view this discussion on the web visit 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.