# Jdbc river **URL:** \ **Category:** Elasticsearch\ **Created:** [September 11, 2013, 12:14pm UTC](https://discuss.elastic.co/t/jdbc-river/13555 "2013-09-11T12:14:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Fabricio\_Archanjo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fabricio_archanjo/32/2112_2.png) [@Fabricio\_Archanjo](https://discuss.elastic.co/u/Fabricio_Archanjo)\ **Post date:** [September 11, 2013, 12:14pm UTC](https://discuss.elastic.co/t/jdbc-river/13555/1 "2013-09-11T12:14:00Z")
Hi All, I'm learning elasticsearch to change my search engine on my website. I have one doubt abou that. Can I add new documents to the index after oneshot? I'd like to add new documents incrementally, is it possible? Thanks for all, Fabricio Archanjo -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [September 11, 2013, 12:57pm UTC](https://discuss.elastic.co/t/jdbc-river/13555/2 "2013-09-11T12:57:55Z")
The JDBC river "oneshot" is thought for quick success, and then forget about it (demo mode). Currently there are some deficiencies (bugs?) to detect new rows. To make it simple, the JDBC river needs some overhaul of the "strategies" design that fetch the data, for becoming more feasible in everyday situations. 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Fabricio\_Archanjo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fabricio_archanjo/32/2112_2.png) [@Fabricio\_Archanjo](https://discuss.elastic.co/u/Fabricio_Archanjo)\ **Post date:** [September 11, 2013, 1:21pm UTC](https://discuss.elastic.co/t/jdbc-river/13555/3 "2013-09-11T13:21:42Z")
> Currently there are some deficiencies (bugs?) to detect new rows. Detect new rows via sql, right? I'd like to add new documents via PUT on elasticsearch. The oneshot is going to make an index once for me, after my app is going to feed this index created by plugin. Thanks Jörg, On Wed, Sep 11, 2013 at 9:57 AM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > The JDBC river "oneshot" is thought for quick success, and then forget > about it (demo mode). > > Currently there are some deficiencies (bugs?) to detect new rows. To make > it simple, the JDBC river needs some overhaul of the "strategies" design > that fetch the data, for becoming more feasible in everyday situations. > > Jörg > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/Td6QJrGMC1k/unsubscribe](https://groups.google.com/d/topic/elasticsearch/Td6QJrGMC1k/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![lebowitz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lebowitz/32/1814_2.png) [@lebowitz](https://discuss.elastic.co/u/lebowitz)\ **Post date:** [September 12, 2013, 2:55am UTC](https://discuss.elastic.co/t/jdbc-river/13555/4 "2013-09-12T02:55:19Z")
You can use Jörg's table strategy, which implements a fixed sliding window of time query. One for an int64 primary key would be nice. -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:17am UTC](https://discuss.elastic.co/t/jdbc-river/13555/5 "2017-07-06T02:17:02Z")