# Elastic 1.5.1 + postgresql **URL:** \ **Category:** Elasticsearch\ **Created:** [April 9, 2015, 8:07pm UTC](https://discuss.elastic.co/t/elastic-1-5-1-postgresql/23178 "2015-04-09T20:07:43Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Fabio\_Ebner](https://avatars.discourse-cdn.com/v4/letter/f/ccd318/32.png) [@Fabio\_Ebner](https://discuss.elastic.co/u/Fabio_Ebner)\ **Post date:** [April 9, 2015, 8:07pm UTC](https://discuss.elastic.co/t/elastic-1-5-1-postgresql/23178/1 "2015-04-09T20:07:43Z")
It's possible to connect the elastic 1.5.1 with my postgresql?? in 1.3.1 I do this with river plugin, but in 1.5.1 I read that river are deprecated. tks -- 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/c9d09e49-62db-40be-9329-4ef356587027%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c9d09e49-62db-40be-9329-4ef356587027%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:** [April 9, 2015, 8:13pm UTC](https://discuss.elastic.co/t/elastic-1-5-1-postgresql/23178/2 "2015-04-09T20:13:31Z")
You can still use the JDBC plugin. It is not only a river, but also a standalone module, similar to Logstash. Jörg On Thu, Apr 9, 2015 at 10:07 PM, Fabio Ebner [fabio.ebner@lumera.com.br](mailto:fabio.ebner@lumera.com.br) wrote: > It's possible to connect the elastic 1.5.1 with my postgresql?? in 1.3.1 I > do this with river plugin, but in 1.5.1 I read that river are deprecated. > > tks > > -- > 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/c9d09e49-62db-40be-9329-4ef356587027%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/c9d09e49-62db-40be-9329-4ef356587027%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/c9d09e49-62db-40be-9329-4ef356587027%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/c9d09e49-62db-40be-9329-4ef356587027%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAKdsXoEPrDddUm17FMvd%2BCbh6PJ%3DQcPMLPseqSqDskEbynut9g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEPrDddUm17FMvd%2BCbh6PJ%3DQcPMLPseqSqDskEbynut9g%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![timbunce](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timbunce/32/44945_2.png) [@timbunce](https://discuss.elastic.co/u/timbunce)\ **Post date:** [April 13, 2015, 10:33am UTC](https://discuss.elastic.co/t/elastic-1-5-1-postgresql/23178/3 "2015-04-13T10:33:58Z")
On Thu, Apr 09, 2015 at 01:07:43PM -0700, Fabio Ebner wrote: > It's possible to connect the elastic 1.5.1 with my postgresql?? in 1.3.1 I do this with river plugin, > but in 1.5.1 I read that river are deprecated. I'm hoping someone will implement a Postgres Foreign Data Wrapper for Elasticsearch. (I'd do it myself by my time is taken elsewhere.) There are many wrappers already, including interfaces to a number of "NoSQL" databases like Cassandra, CouchDB, MongoDB, RethinkDB etc: [https://wiki.postgresql.org/wiki/Foreign\_data\_wrappers](https://wiki.postgresql.org/wiki/Foreign_data_wrappers) The Multicorn project [http://multicorn.org](http://multicorn.org) is a PostgreSQL extension to make Foreign Data Wrapper development easy by allowing the programmer to use the Python programming language. It ought to be simple to implement a PostgreSQL FDW for Elasticsearch using Multicorn and the Elasticsearch Python API. The end result would be that Elasticsearch data would appear as tables in your Postgres database. You could then insert, delete, update and select Elasticsearch data from within Postgres. Here are the slides for "Write a Foreign Data Wrapper in 15 minutes": > **[Conferences-write\_a\_foreign\_data\_wrapper\_in\_15\_minutes-presentation.pdf](https://wiki.postgresql.org/images/7/7e/Conferences-write_a_foreign_data_wrapper_in_15_minutes-presentation.pdf)** > > 580.63 KB Tim. -- 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/20150413103358.GI1536%40timac-2.local](https://groups.google.com/d/msgid/elasticsearch/20150413103358.GI1536%40timac-2.local). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:20am UTC](https://discuss.elastic.co/t/elastic-1-5-1-postgresql/23178/4 "2017-07-06T00:20:06Z")