so far i understood, you need both columns in your database table.
Otherwise the river wont be able to do the checks. The river compares the
updated_at date with own date. If that date equal or in the future than the
one from the river, the river try to update/insert your record to
Hi I am new to ES but my company is starting to use it
When I set up an river I have scheduled it to check for data changes at an
30 min interval, my largest index on dev includes 230k documents but in
production is expected to grow to 300million docs
this 230k index is a heavy load on the
Hi Erlendur,
In your case, you should use the column strategy instead of simple one. The
column strategy requires two columns in the SQL DB.
- cerated_at
- update_at
Cheers, Ramy
Am Dienstag, 25. November 2014 11:04:17 UTC+1 schrieb Erlendur Hákonarson:
Hi I am new to ES but my company is
Sorry...
- created_at
- updated_at
Am Dienstag, 25. November 2014 11:55:18 UTC+1 schrieb Ramy:
Hi Erlendur,
In your case, you should use the column strategy instead of simple one.
The column strategy requires two columns in the SQL DB.
- cerated_at
- update_at
Cheers, Ramy
Am Dienstag,
Thanks Ramy
but how does that strategy work
is there any doc on strategies I can view?
the only one I found was on the jprante github wiki and that only describes
the simple strategy
and if I am using tables from a system that I have no control over and
those columns created_at and updated_at
maybe this link will helps you:
https://github.com/jprante/elasticsearch-river-jdbc/pull/137
and this code snippet:
{
*strategy: column,*
type: jdbc,
jdbc: {
url: db server connect string,
user: username,
schedule: 0 20/30 * * * ?,
password: password,
index:
