JDBC River wirh table strategy --- the table "my_jdbc_river_ack" is not updated?

Elastic Stack Elasticsearch
1

Hye,

When I'm using the jdbc river with the "table" strategy.
It seems that the table "my_jdbc_river_ack" is not updated.

Is it normal ?

Thanks,

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

Unfortunately, the "table" strategy is not well tested in the JDBC river.
You may run into bugs of all kind. I hope I can continue working on the
strategies soon and push out a new release. Patches are welcome!

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.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thanks Jörg,
I'm waiting the new release to use the "table" strategy and I'm candidate
to test this one when it will be pushed out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.