# Is jdbc river is going to expire? If yes then what is the alternative to connect the database **URL:** \ **Category:** Elasticsearch\ **Created:** [May 11, 2015, 12:19pm UTC](https://discuss.elastic.co/t/is-jdbc-river-is-going-to-expire-if-yes-then-what-is-the-alternative-to-connect-the-database/497 "2015-05-11T12:19:18Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [May 11, 2015, 8:37pm UTC](https://discuss.elastic.co/t/is-jdbc-river-is-going-to-expire-if-yes-then-what-is-the-alternative-to-connect-the-database/497/2 "2015-05-11T20:37:18Z")
JDBC river for ES 1.5 and higher will be followed by a standalone JVM solution, a JDBC feeder, which uses transport client, with only small changes to JSON river specification syntax. Existing river versions of JDBC river will be supported until ES versions 1.3 and 1.4 will reach end of updates. I will publish a document how to move to the standalone JDBC feeder so transition will be smooth. If you want to have a glimpse at the upcoming source code, look at the "noriver" branch at [https://github.com/jprante/elasticsearch-jdbc/tree/noriver](https://github.com/jprante/elasticsearch-jdbc/tree/noriver) (the README is still work in progress) --- _[View the full topic](https://discuss.elastic.co/t/is-jdbc-river-is-going-to-expire-if-yes-then-what-is-the-alternative-to-connect-the-database/497)._