# Painful! postgres--\>logstash--\>elasticsearch mapper\_parsing\_exception!

**URL:** <https://discuss.elastic.co/t/painful-postgres-logstash-elasticsearch-mapper-parsing-exception/44918>\
**Category:** Elasticsearch\
**Created:** [March 20, 2016, 3:23am UTC](https://discuss.elastic.co/t/painful-postgres-logstash-elasticsearch-mapper-parsing-exception/44918 "2016-03-20T03:23:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [March 20, 2016, 1:26pm UTC](https://discuss.elastic.co/t/painful-postgres-logstash-elasticsearch-mapper-parsing-exception/44918/3 "2016-03-20T13:26:02Z")

</div>

> [@past2010yeah](#):
>
> I think the problem is elasticsearch can't parse the geojson string data I exported from postgres

FYI my JDBC importer [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-jdbc) can parse GeoJSON points and shapes from PostgreSQL.

If there are problems, you can ask for help at [Issues · jprante/elasticsearch-jdbc · GitHub](https://github.com/jprante/elasticsearch-jdbc/issues)

---

_[View the full topic](https://discuss.elastic.co/t/painful-postgres-logstash-elasticsearch-mapper-parsing-exception/44918)._