# JDBC river in production environment

**URL:** <https://discuss.elastic.co/t/jdbc-river-in-production-environment/21752>\
**Category:** Elasticsearch\
**Created:** [January 21, 2015, 4:02pm UTC](https://discuss.elastic.co/t/jdbc-river-in-production-environment/21752 "2015-01-21T16:02:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abid\_Hussain](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Abid\_Hussain](https://discuss.elastic.co/u/Abid_Hussain)\
**Post date:** [January 21, 2015, 4:02pm UTC](https://discuss.elastic.co/t/jdbc-river-in-production-environment/21752/1 "2015-01-21T16:02:28Z")

</div>

Hi all,

I'm quite new to ES and wonder how/if jdbc river is ready for indexing  
RDBMS in production enviromnent as in GitHub  
[https://github.com/jprante/elasticsearch-river-jdbc#river-or-feeder](https://github.com/jprante/elasticsearch-river-jdbc#river-or-feeder) it  
says about River:  
_about to be deprecated by Elasticsearch core team_

So is it a good idea to use jdbc river or is there a better strategy?

Regards,

Abid

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/a9bc1c06-a829-488e-8c33-1d99e63fa19b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/a9bc1c06-a829-488e-8c33-1d99e63fa19b%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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, 12:37am UTC](https://discuss.elastic.co/t/jdbc-river-in-production-environment/21752/2 "2017-07-06T00:37:33Z")

</div>


